═══ 1. NOTICES ═══ The following paragraph does not apply to the United Kingdom or any country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This publication could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time. It is possible that this publication may contain reference to, or information about, IBM products (machines and programs), programming, or services that are not announced in your country. Such references or information must not be construed to mean that IBM intends to announce such IBM products, programming, or services in your country. Requests for technical information about IBM products should be made to your IBM Authorized Dealer or your IBM Marketing Representative. References in this publication to IBM products, programs, or services do not imply that IBM intends to make these available in all countries in which IBM operates. Any reference to an IBM product, program or service is not intended to state or imply that only IBM's product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any of IBM's intellectual property rights or other legally protected rights may be used instead of the IBM product, program, or service. Evaluation and verification of operation in conjunction with other products, programs, or services, except those expressly designated by IBM, are the user's responsibility. IBM may have patents or pending patent applications covering subject matter in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to the IBM Director of Commercial Relations, IBM Corporation, Purchase, NY 10577. ═══ 1.1. Trademarks and Service Marks ═══ Terms in this publication that are trademarks of the IBM Corporation in the United States and/or other countries. These include: IBM 8516 Touch Display Micro Channel Operating System/2 OS/2 PS/2 WIN-OS/2 Workplace Shell XGA Other trademarks appearing in this publication are owned by their respective companies. Logitech, Trackman, Mouseman are trademarks of Logitech Corporation. Microsoft, MS Excel, and Windows are trademarks of Microsoft Corporation. IBM DISCLAIMS ALL WARRANTIES, WHETHER EXPRESSED OR IMPLIED, INCLUDING WITHOUT LIMITATION, WARRANTIES OF FITNESS AND MERCHANTABILITY WITH RESPECT TO THE INFORMATION IN THIS DOCUMENT. BY FURNISHING THIS DOCUMENT, IBM GRANTS NO LICENSES TO ANY RELATED PATENTS OR COPYRIGHTS. Copyright IBM Corporation, 1993, all rights reserved. ═══ 1.2. Authors ═══ COMPILED AND WRITTEN BY CRAIG S. EUBANKS IBM OS/2 Technical Support & GORDON WEBSTER IBM OS/2 Development Revision 3.0 1993 ═══ 2. INTRODUCTION ═══ This document was created out of necessity generated by the activities of the OS/2 technical support team at Boca Raton IBM. It is an attempt to compile all the information related to pointing devices and the various versions of OS/2, including 1.3, 2.0, and service pack. It is hoped that this will be of use to all those involved in the support process, as well as anyone trying to solve their own problem. There are both technical sections on device drivers and certain types of OEM mice, as well as a common problem/answer section for quick reference while working with customer problems. This work is constantly evolving as new info comes in. At some point it will likely be made an on line document so the any changes will be real time. If you have two or more copies, check the date and version number to see which is the most current. The authors would like to thank Andy Frankford and Ed Lozano of the MKBCMP Warranty Support Team for their help in converting this document from text to the format as it now appears Note: All references to C: in this document assume that OS/2 2.0 is installed on the C partitiion. If this is not true, simply change C to the partition drive letter upon which user has installed OS/2. ═══ 3. MOUSE DEVICE DRIVERS ═══ There are basically two main device drivers for pointing devices in OS/2 2.x. A Physical Device Driver (PDD) called MOUSE.SYS, and a Virtual Mouse Drive (VMD) called VMOUSE.SYS. ═══ 3.1. Physical Device Drivers ═══ Two classes of pointing devices are supported, relative and absolute. A relative pointing device reports relative motion ie.how far the device has moved. An example of a relative pointing device is a mouse, or a track ball. An absolute pointing device reports absolute positions within some predefined work space. An example of an absolute pointing device is a touch-sensitive screen. Some commonly used pointing device terms and their definitions: Term Definition MOUSE$ The OS/2 system-provided pointing device driver name, which is defined in the device header field of MOUSE.SYS. IDC Inter-Device Communication. Device-Independent Device Driver Another way of referring to MOUSE.SYS, which handles all the IDC interfaces for pointing devices. Device-Dependant Device Driver Hardware-specific device driver that communicates with MOUSE.SYS through the IDC for additional pointing device support. The OS/2 operating system provides pointing support for the following: IBM Mouse IBM 8516 Touch Display Microsoft Mouse Logitech Mouse Note: Any pointing device which is compatible with the above devices will be supported. ═══ 3.1.1. Generic Pointing Device Support ═══ The OS/2 operating system provides a physical mouse device driver called MOUSE.SYS that will attempt to detect the type of pointing device currently installed on the system. Once it detects the existence of a particular pointing device, it dynamically sets up support for that device. The search order for a pointing device is as follows: 1. Pointing Device Interface (PDI) port. Also known as 'PS/2 Style' port. 2. Serial ports. COM1 then COM2. 3. Inport. (AT bus only). 4. Bus card. If the physical Mouse device driver is unable to detect the presence of a pointing device, the install program will prompt the user for pointing device information. The install program then sets the appropriate statement for the pointing device support in the config.sys file. The physical Mouse driver will set up to support the first pointing device that it finds. ═══ 3.1.2. High-Level Design ═══ During device driver intialization time, the physical Mouse device driver first checks to see if the TYPE= overrider has been used. If the DEVICE=C:\OS2\MOUSE.SYS line in the CONFIG.SYS contains a TYPE= overrider, then pointing device support is established through an IDC interface with the device-dependent device driver name following TYPE=. The device-dependent device driver must be loaded before MOUSE.SYS. If a TYPE= overrider has not been specified, it is assumed that generic pointing device support is desired. The generic device driver detects if the system is a Family1- (non-ABIOS) system, or a Family-2 (ABIOS) system. ═══ 3.1.3. Physical Mouse Device Driver Considerations ═══ System Install ensures that physical Mouse device driver initialization takes place prior to physical ASYNC device driver initialization (COM port device drivers). This allows the physical ASYNC device driver to determine that it is not responsible for servicing the port which the device is installed on, which ensures that physical Mouse device drivers are not preempted from the COMx ports by the physical ASYNC device drivers. Note: When manually changing CONFIG.SYS, the user must place the mouse DEVICE= statements before ASYNC DEVICE= statements (COM.SYS, and VCOM.SYS). ═══ 3.1.4. Adding Support for a Unique Pointing Device (OEM) ═══ OS/2 provides a method for supporting additional pointing devices. Pointing device support can be obtained by writing a device-dependent device driver MOUSE.SYS, that is, the device-independent device driver, through the IDC interfaces. For further information consult the REFERENCES section for IBM Physical Device Driver Reference Manual. Additional information on developing unique device drivers can be obtained through the Developers Assistance Program at IBM. See the OEM MOUSE DRIVERS section of this document. ═══ 3.1.5. Relaxed Option ═══ In version 2.1 of OS/2, there has been an option added called "RELAXED". This can be used with any three button mouse if the mouse pointer is jumping randomly about the screen. Do not use this parameter unless you are experiencing this problem. To use, just add the word RELAXED to the end of the DEVICE= ....\MOUSE.SYS line in the CONFIG.SYS file. ═══ 3.2. Virtual Mouse Driver ═══ The Intel 80386 processor has a feature which allows a DOS program to run in its own one meg address space. This effectively isolates it from the rest of the programs running on the system. This special mode is called the Virtual 8086 Mode, and is utilized by OS/2 to run DOS applications in their own memory partition. This is known as a Virtual DOS Machine (VDM) in OS/2. OS/2 can support a large number of these VDM's at one time. The DOS programs run in their own VDM without any knowledge of other programs running on the system. DOS programs that write directly to the system hardware or devices are permitted to run in a DOS session. When the program writes directly to a device or the hardware, the operation is trapped by the kernel and routed to a Virtual Device Driver (VDD). The VDD is a special type of driver that emulates the functions of a particular hardware device, such as a mouse or COM port. The VDD appears as the actual device to the application, but direct access to the device is in reality performed through a Physical Device Driver (PDD), such as MOUSE.SYS. The MOUSE.SYS PDD reads from and writes to the device, and passes the results to the VDD. The VDD will then send the results to the DOS application. VDDs are loaded at system boot time after any PDDs, but before the Presentation Manager shell is started. The VDD will not load if the associated PDD is not loaded. In the case of devices, if MOUSE.SYS does not find a pointing device on the system it will not load itself, and thus the virtual mouse driver VMOUSE.SYS will also not be loaded by the system. This results in the "SYS1201 VMOUSE.SYS not loaded..." error. When the DOS session is exited, the VDD must perform any clean-up that is necessary. The usually includes releasing any allocated memory and restoring the state of the device, in this case the mouse. In OS/2 , DOS applications which require the use of a pointing device are supported via the INT 33h interface. There are no restrictions on any use of the INT 33H interface, even when a DOS session is in background mode. This interface will perform the following functions o Position and button tracking and notification o Selectable pixel and mickey mappings o Pointer location and shape o Video mode tracking o Emulation of a light pen MOUSE.SYS is aware of which session currently owns the pointing device. Thus when a DOS full-screen session owns the pointing device, MOUSE.SYS notifies the virtual device driver of mouse type events. In the case of a DOS window, MOUSE.SYS will route events through the Presentation Manager, which in turn will route them to the virtual mouse driver. The Mouse Exclusive Access DOS setting can be set to on for the DOS windowed sessions, which will then bypass the presentation manager causing mouse events to be sent directly from MOUSE.SYS to the virtual mouse driver. This option is useful for applications which draw and track their own pointing device, and will cure the problem of having two pointers (arrows) show on the screen in a DOS window. ═══ 3.3. Virtual Touch Device Driver ═══ The Virtual Touch Device Driver (VTOUCH) provides support for the INT 7FH for multiple DOS sessions. This VDD is limited (by default) to making actual touch XYZ data available only to full screen DOS programs because the PDD, which handles the touch data interrupts, cannot determine which window to send the touch to when running with the Presentation Manager session in the foreground. The physical Mouse device driver can determine which window to send the mouse data to because it is able to feed the single queue of the Presentation Manager, which can then determine which window is to receive the event. If the window is a DOS window, it calls the virtual device driver. ═══ 4. OEM MOUSE DRIVERS ═══ The mouse device driver is layered allowing any OEM to easily add support for their pointing device. By writing a small mouse device dependent device driver they can get their device to work with OS/2 . There is MOUSE.SYS source code provided in theDDK (Device Driver Kit) for developers to reference. Please contact the OEM manufacturer to find out if they provide a device driver for OS/2 (or are in the process of developing). Any OEM pointing device manufacturers should be referred to the Developers Assistance Program at IBM if they require further assistance. They should also reference the IBM technical publications on OS/2, some of which are listed in the REFERENCES section at the end of this document. IBM publications can be ordered by calling one of the following numbers ┌───────────────────────────────────┬──────────────────┐ │Developers Assistance Program (DAP)│407 - 982 - 6408 │ │at IBM │ │ ├───────────────────────────────────┼──────────────────┤ │IBM DIRECT (supplies: place orders,│800-IBM-2468 │ │get prices) │(426-2468) │ ├───────────────────────────────────┼──────────────────┤ │IBM OS/2 Information and Sales │800-3IBM-OS2 │ │ │(342-6672) │ ├───────────────────────────────────┼──────────────────┤ │IBM PC Technical Books Hotline │800-IBM-PCTB │ │ │(426-7282) │ └───────────────────────────────────┴──────────────────┘ An example of an OEM manufacturer that provides OS/2 support is Hewlett Packard. HP provides HILMOU.SYS and NOEXBIOS.SYS device drivers. Below is the instructions for adding support for the Hewlett Packard HIL mouse. This mouse has its own unique connector which looks similar to a phone jack. Customers should go to their dealer for the diskette that contains HP mouse support. Customers may also access the files on Compuserve by typing "COMPUSERV GO HP". As a last resort they can call HP at HP Customer Service. The number is 1-800-752-0900. Directions for installing a Hewlett Packard mouse and drivers. 1. Select PS/2 mouse during system installation at the Pointing Device selection panel. 2. Copy HILMOU.SYS and NOEXBIOS.SYS to C:\OS2 (these are supplied by HP) 3. Update the CONFIG.SYS file with the following statements in the order shown: add DEVICE=C:\OS2\NOEXBIOS.SYS add DEVICE=C:\OS2\HILMOU.SYS modify DEVICE=C:\OS2\MOUSE.SYS TYPE=HILMOU$ (This line should already be in the CONFIG.SYS but will need the TYPE=... added ) 4. Reboot the system. Note: All references to "C:" in this document assume that OS/2 is installed on the "C" partitiion. If this is not true, simply change "C" to the partition drive letter upon which user has installed OS/2. ═══ 5. INSTALL PROCESS ═══ There are important differences in the install process between version 2.0 and version 2.1. The changes were made in an attempt to reduce the confusion which caused to overide the systems choice of mouse driver, and resulted in the incorrect statements to be added to the CONFIG.SYS file. The following sections will describe the install process for Version 2.0 and the differences in Version 2.1 ═══ 5.1. Version 2.0 ═══ During the install process, the mouse physical device driver, MOUSE.SYS, will attempt to detect a pointing device. If a device is detected, you will NOT be shown a mouse selection panel during the processing of diskette 2. Once the system is rebooted to finish the installation, it is highly recommended that you do NOT go into the PM mouse panel to change anything. Many customers are selecting a mouse from this panel and are forcing a different device type than what was detected. A prime example of this is the Logitech series M mouse. This mouse is Microsoft compatible, and will be detected automatically. The mouse panel will read MS Serial Mouse. Many customers are then going into the Presentation Manager panel and choosing Logitech Serial. This choice will add the PCLOGIC.SYS driver which does NOT work for the Logitech series M-mouse. The bottom line is that if you are not prompted for any mouse information or have a mouse pointer during the first part of the install process, do not change the settings in the graphical mouse selection panel. Also note that if the selective install was used for any reason, it has been known to leave undesirable statements behind. For example, if the person by mistake originally chose a Logitech mouse, when in fact they had a MS compatible, then later did selective install back to PS/2 Style pointing device (the MS compatible selection), on occasion the statements (shown in bold) DEVICE=C:\OS2\PCLOGIC.SYS SERIAL=COMx (where 'x' is 1 or 2) DEVICE=C:\OS2\MOUSE.SYS TYPE=PCLOGIC$ have been left behind. This will cause various problems when in fact the user believes everything should be okay. Check the config.sys file and see if there are erroneous statements. Note: All references to "C:" in this document assume that OS/2 is installed on the "C" partition. If this is not true, simply change "C" to the partition drive letter upon which user has installed OS/2. ═══ 5.2. Version 2.1 ═══ In version 2.0, many users did not realize that the system would attempt to detect what pointing device was connected to the system, and would install the appropriate drivers. When the panel came up asking if the choice was correct, many users believed that it was asking them to make a selection, and thus they did. This led to many incorrect choices due to the layout of the panel itself and the choices it provided. There was a choice for Logitech, but this was only for the non-Microsoft compatible versions, thus those with the more recent Logitech mice would end up with an incorrect install if they chose the Logitech selection. Install for 2.1 will attempt to detect a pointing device on the system, and then display the choice, but will display the choice on a separate panel from the one with the available choices. This will hopefully avoid confusion for the user. If it unable to detect the mouse, or the user wishes to see the other available choices, a second panel will come up with the following selections o PS/2 (tm) Style Pointing Device o Serial Pointing Device o Logitech (tm) C-Series Serial Mouse o Logitech M-Series Mouse o IBM Touch Device o PC Mouse Systems (tm) Mouse o Other Pointing Device for Mouse Port o No Pointing Device Support This list will give an indication of which mouse is currently selected by a black dot next to the selection and a box around the lettering. If this looks correct hit OK and install will continue. If this is a Selective Install, then hit Cancel if selection is already correct or OK if a change was made. If user is uncertain as to which selection, they can consult the Readme file that comes with OS/2. ═══ 6. CONFIG.SYS STATEMENTS ═══ There are hundreds of pointing devices available today. Most of these are Microsoft compatible and if they are 100% MS compatible OS/2 supports them. The installation program of OS/2 has the ability to automatically detect Microsoft compatible mice during the install process and will install the correct support for those mice. For those compatible pointing devices, the MOUSE.SYS device driver will detect them during the install process and the OS/2 install program will add the following lines for mouse support to the CONFIG.SYS system file. DEVICE=C:\OS2\POINTDD.SYS DEVICE=C:\OS2\MOUSE.SYS. DEVICE=C:\OS2\MDOS\VMOUSE.SYS There are other pointing devices, that are not detectable by MOUSE.SYS. Although these devices are not autodetected, they are still supported (except at this time the Mouse Systems and Kensington bus/serial mouse cards, see COMMON PROBLEMS & SOLUTIONS ). The OS/2 install program will add the following lines for mouse support to the CONFIG.SYS system file for certain undetectable pointing devices, when the LOGITECH selection is made from the mouse installation panel: DEVICE=C:\OS2\POINTDD.SYS DEVICE=C:\OS2\PCLOGIC.SYS SERIAL=COMx (where 'x' is 1 or 2) DEVICE=C:\OS2\MOUSE.SYS TYPE=PCLOGIC$ DEVICE=C:\OS2\MDOS\VMOUSE.SYS Warning: Serial pointing device support for COM ports above COM2 is available only on machines that allow interrupt sharing such as IBM PS/2 and EISA machines. The following are the lines which will be installed in the stated subdirectories and will be referenced in the file CONFIG.SYS in the booted drives root directory. (The assumption is that the boot drive is the "C:" drive) 1. PDI Port: For any mouse designed to run in the "PS/2" style round mouse port (PDI port) located on the planar next to the keyboard port. Usually PS/2's but there are some clones with PDI mouse ports. These devices are Microsoft Compatible. DEVICE=C:\OS2\MDOS\VMOUSE.SYS DEVICE=C:\OS2\POINTDD.SYS DEVICE=C:\OS2\MOUSE.SYS DEVICE=C:\OS2\COM.SYS 2. MS Compatible Serial: Serial mice designed to run on a communications port (either a DB9 pin connector or DB25 pin connector) and run under the MicroSoft INT 33 mouse interface. DEVICE=C:\OS2\MDOS\VMOUSE.SYS DEVICE=C:\OS2\POINTDD.SYS DEVICE=C:\OS2\MOUSE.SYS DEVICE=C:\OS2\COM.SYS 3. Mouse Systems Compatible and Logitech C-series: Serial mice designed to run on a communications port and are not run under the MicroSoft INT 33 mouse interface. DEVICE=C:\OS2\MDOS\VMOUSE.SYS DEVICE=C:\OS2\POINTDD.SYS DEVICE=C:\OS2\PCLOGIC.SYS SERIAL=COMx (where x is 1 or 2) DEVICE=C:\OS2\MOUSE.SYS TYPE=PCLOGIC$ DEVICE=C:\OS2\COM.SYS Note: Most Logitech devices are MicroSoft compatible and will install as 1) or 2) above. This is for C series only, a collection of older pointing devices, which are not MS compatible. ═══ 7. OS/2 COMPATIBLE DEVICES ═══ We have found that some devices are not 100% compatible and therefore are not supported. But for those pointing devices that OS/2 does support, the following is a list that shows the proper configuration associated for each model. This list shows just those pointing devices that have been tested by IBM, or are known to work, but does not limit the support to only those that are listed. Note: This list is not complete! ┌────────────────────┬──────────┬─────────────┬────────┬────────┐ │Description │Type │Model# │Config │Buttons │ │ │ │ │Type │ │ ├────────────────────┼──────────┼─────────────┼────────┼────────┤ │Appoint Mouse Pen │PS/2 │Square Body │Type 1 │2 │ ├────────────────────┼──────────┼─────────────┼────────┼────────┤ │Appoint Mouse Pen │PS/2 │Round Body │Type 1 │2 │ ├────────────────────┼──────────┼─────────────┼────────┼────────┤ │Appoint Mouse Pen │Serial │Round Body │Type 1 │2 │ ├────────────────────┼──────────┼─────────────┼────────┼────────┤ │Appoint Thumbelina │PS/2 │N/A │Type 1 │2 │ ├────────────────────┼──────────┼─────────────┼────────┼────────┤ │Appoint Thumbelina │Serial │N/A │Type 1 │2 │ ├────────────────────┼──────────┼─────────────┼────────┼────────┤ │C&H Products │Serial │400-501 (ps2│Type 1 │2 │ │Rollermouse │ │400-502, bus │ │ │ │ │ │400-503) │ │ │ ├────────────────────┼──────────┼─────────────┼────────┼────────┤ │Chicony Keyboard w/ │Serial │N/A │Type 2 │3 │ │Trackball │ │ │ │ │ ├────────────────────┼──────────┼─────────────┼────────┼────────┤ │CLIXes (by Genius) │Serial │CX-3500 │Type 3 │2/3 │ ├────────────────────┼──────────┼─────────────┼────────┼────────┤ │Dexxa Mouse │Serial │N/A │Type 1 │2 │ ├────────────────────┼──────────┼─────────────┼────────┼────────┤ │Genius LC Mouse │Serial │serial │Type 2 │3 │ ├────────────────────┼──────────┼─────────────┼────────┼────────┤ │Genius Mouse One │Serial │serial 3B │Type 3 │2/3 │ ├────────────────────┼──────────┼─────────────┼────────┼────────┤ │Genius GM-D321 │Serial │GM-D321 │Type 3 │2/3 │ ├────────────────────┼──────────┼─────────────┼────────┼────────┤ │Genius Serial :& │Multiple │GM-F203 │Type 3 │2/3 │ │PS/2 │ │ │ │ │ ├────────────────────┼──────────┼─────────────┼────────┼────────┤ │Genius Wireless │Serial │GM-W220 │Type 1 │2 │ ├────────────────────┼──────────┼─────────────┼────────┼────────┤ │Genius Genie TRAC │Multiple │HI-TRAC │Type 3 │2/3 │ ├────────────────────┼──────────┼─────────────┼────────┼────────┤ │IBM PS/2 │PS/2 │33G3835 │Type 1 │2 │ ├────────────────────┼──────────┼─────────────┼────────┼────────┤ │IBM PS/2 │PS/2 │6450350 │Type 1 │2 │ ├────────────────────┼──────────┼─────────────┼────────┼────────┤ │IBM PS/2 "dove bar" │PS/2 │33G5430 │Type 1 │2 │ ├────────────────────┼──────────┼─────────────┼────────┼────────┤ │IBM PS/2 RISC 6000 │PS/2 │M-SB9-6MD │Type 1 │3 │ ├────────────────────┼──────────┼─────────────┼────────┼────────┤ │IBM Trackpoint II │PS/2 │N/A │Type 1 │2 │ ├────────────────────┼──────────┼─────────────┼────────┼────────┤ │IBM Track\Mouse │PS/2 │1396670 │Type 1 │2 │ │combo │ │ │ │ │ ├────────────────────┼──────────┼─────────────┼────────┼────────┤ │IBM Touch Display │other │8516 │Type 4 │2 │ ├────────────────────┼──────────┼─────────────┼────────┼────────┤ │Kensington Expert │Serial │62368 │Type 1 │2 │ ├────────────────────┼──────────┼─────────────┼────────┼────────┤ │Kensington Expert │PS/2 │62368 │Type 1 │2 │ ├────────────────────┼──────────┼─────────────┼────────┼────────┤ │Kensington Serial │Serial │62364 │Type 1 │2 │ ├────────────────────┼──────────┼─────────────┼────────┼────────┤ │Lexmark Keyboard w/ │PDI │1398155 │Type 1 │3 │ │Trackball │ │ │ │ │ ├────────────────────┼──────────┼─────────────┼────────┼────────┤ │Lexmark Keyboard w/ │PDI │1398799 │Type 1 │3 │ │Trackball │ │ │ │ │ ├────────────────────┼──────────┼─────────────┼────────┼────────┤ │Logitech Mouseman │Serial │M-MC13-DB9F │Type 1 │3 │ ├────────────────────┼──────────┼─────────────┼────────┼────────┤ │Logitech Mouseman │Serial │M-RB24 or │Type 1 │3 │ │Cordless │ │M-RA12 │ │ │ ├────────────────────┼──────────┼─────────────┼────────┼────────┤ │Logitech Mouseman │Serial/PDI│M-CJ13 │Type 1 │3 │ │Combo │ │ │ │ │ ├────────────────────┼──────────┼─────────────┼────────┼────────┤ │Logitech Mouseman │Bus │M-PD13-9MD │Type 1 │3 │ │Bus │ │ │ │ │ ├────────────────────┼──────────┼─────────────┼────────┼────────┤ │Logitech Trackman │Serial │T-CC2-9F │Type 1 │3 │ ├────────────────────┼──────────┼─────────────┼────────┼────────┤ │Logitech Trackman │Serial │T-CA1-9F │Type 2 │3 │ ├────────────────────┼──────────┼─────────────┼────────┼────────┤ │Logitech Series 9 │PS/2 │CE9-6MD │Type 1 │3 │ ├────────────────────┼──────────┼─────────────┼────────┼────────┤ │Logitech Series 9 │Serial │CC-93-9F │Type 2 │3 │ ├────────────────────┼──────────┼─────────────┼────────┼────────┤ │Logitech Series 2 │PS/2 │2-7S │Type 1 │2 │ ├────────────────────┼──────────┼─────────────┼────────┼────────┤ │Logitech Mouse │Serial │CA-93-6MD │Type 2 │3 │ ├────────────────────┼──────────┼─────────────┼────────┼────────┤ │Logitech Mouse │Serial │P7-3F │Type 2 │3 │ ├────────────────────┼──────────┼─────────────┼────────┼────────┤ │Marstek │Serial │E22 │Type 1 │3 │ ├────────────────────┼──────────┼─────────────┼────────┼────────┤ │Microsoft Bus │Bus │Green Buttons│Type 1 │2 │ ├────────────────────┼──────────┼─────────────┼────────┼────────┤ │Microsoft Inport │Inport │Grey Buttons │Type 1 │2 │ ├────────────────────┼──────────┼─────────────┼────────┼────────┤ │Microsoft Inport │Multiple │N/A │Type 1 │2 │ ├────────────────────┼──────────┼─────────────┼────────┼────────┤ │Microsoft Serial │Serial │Grey Buttons │Type 1 │2 │ ├────────────────────┼──────────┼─────────────┼────────┼────────┤ │Microsoft Serial │Serial │N/A │Type 1 │2 │ ├────────────────────┼──────────┼─────────────┼────────┼────────┤ │Microsoft BallPoint │Serial │11340 │Type 1 │2/4 │ ├────────────────────┼──────────┼─────────────┼────────┼────────┤ │Microsoft BallPoint │PS/2 │11340 │Type 1 │2/4 │ ├────────────────────┼──────────┼─────────────┼────────┼────────┤ │MicroSpeed PC-Trac │Serial/Bus│N/A │Type 1 │3 │ │Trackball │ │ │ │ │ ├────────────────────┼──────────┼─────────────┼────────┼────────┤ │Microspeed FastTRAP │Serial/Bus│N/A │Type 1 │3 │ │Trackball │ │ │ │ │ ├────────────────────┼──────────┼─────────────┼────────┼────────┤ │Microspeed MicroTRAC│Serial │N/A │Type 1 │3 │ ├────────────────────┼──────────┼─────────────┼────────┼────────┤ │Mouse Systems PC │Serial │402462-001 │Type 3 │2/3 │ │Mouse III │ │ │ │ │ ├────────────────────┼──────────┼─────────────┼────────┼────────┤ │Mouse Systems Little│Serial │402462-001 │Type 3 │2 │ │Mouse/PC │ │ │ │ │ ├────────────────────┼──────────┼─────────────┼────────┼────────┤ │Mouse Systems │Serial │403470-001 │Type 3 │2 │ │OmniMouse II │ │ │ │ │ ├────────────────────┼──────────┼─────────────┼────────┼────────┤ │Mouse Systems White │Serial │403303-001 │Type 3 │2/3 │ │Mouse III │ │ │ │ │ ├────────────────────┼──────────┼─────────────┼────────┼────────┤ │Mouse Systems │Serial │N/A │Type 1 │2/3 │ │Optical │ │ │ │ │ ├────────────────────┼──────────┼─────────────┼────────┼────────┤ │Mouse Systems │Serial │901794 │Type 2 │3 │ │Optical (red led) │ │ │ │ │ ├────────────────────┼──────────┼─────────────┼────────┼────────┤ │Visi On Optical │Serial │M1 │Type 2 │2 │ ├────────────────────┼──────────┼─────────────┼────────┼────────┤ │Visi On Optical │Serial │M2 │Type 2 │2 │ └────────────────────┴──────────┴─────────────┴────────┴────────┘ Of the above listed pointing devices, any that are of Type 1 are those that are automatically detected by the MOUSE.SYS device driver and do not need a Device Dependant device driver like PCLOGIC.SYS. The IBM Trackpoint II is the pointing "stick" that comes with certain IBM portables. It is a flexible black or red rubber piece in between the G & H keys which moves the pointer, and looks like a pencil eraser. It is hardwired through the mouse port. There are two types of Mouse Systems Optical mice, The most recent version of the optical mouse. It uses an infrared LED (not visible to the eye), has white buttons, and has a switch for 2 or 3 button operation. There is and earlier version of this mouse which is 3 button only, uses a red LED, and has grey buttons. This earlier version will work as a serial mouse with OS/2 , but has been known to have hardware problems. Note: Some Logitech and other early mice have their hardware set to an unknown state,(from a MOUSE.SYS standpoint), while in DOS mode. Do one of the following: 1) Go into Native Dos and issue the command: MOUSE PC ( COM 1 is default) or MOUSE 2 PC ( COM 2 needs to be stated ) Then reboot system(cold or warm boot). Mouse should then work in OS/2. NOTE: must use the mouse.com supplied with mouse for this DOS mouse driver to work. Primarily for Logitech mice. 2) Power system down and restart to clear mouse state. ═══ 7.1. CONFIG.SYS statements ═══ The following pages will describe the CONFIG.SYS statements for devices utilizing different types of protocol. For those devices which do not need a custom driver, there are basically three sets of statements, Type 1, Type 2, and Type 4. Type 3 is for those devices which can use more than one protocol. Of the listed pointing devices, any that are of Type 1 are those that are automatically detected by the MOUSE.SYS device driver and do not need a Device Dependant device driver like PCLOGIC.SYS. Type 1 devices are those which are Microsoft Compatible. Type 2 devices are those which are Mouse Systems Compatible. ═══ 7.1.1. Type 1 CONFIG.SYS Statements ═══ These statements are for any device which is 100% Microsoft compatible. Only supports 2 button mode. DEVICE=C:\OS2\MDOS\VMOUSE.SYS DEVICE=C:\OS2\POINTDD.SYS DEVICE=C:\OS2\MOUSE.SYS ═══ 7.1.2. Type 2 CONFIG.SYS Statements ═══ These are the correct statements for any mouse which uses the Mouse Systems mode. These are generally 3-button mice, but do not have to be such. Many of the older Logitech devices will use these statements. DEVICE=C:\OS2\MDOS\VMOUSE.SYS DEVICE=C:\OS2\POINTDD.SYS DEVICE=C:\OS2\PCLOGIC.SYS SERIAL=COMx DEVICE=C:\OS2\MOUSE.SYS TYPE=PCLOGIC$ ( where 'x' is the COM port number. Either 1 or 2) ═══ 7.1.3. Type 3 CONFIG.SYS Statements ═══ o If the mouse is set on 2 button mode or Microsoft mode then use the Type 1 configuration. DEVICE=C:\OS2\MDOS\VMOUSE.SYS DEVICE=C:\OS2\POINTDD.SYS DEVICE=C:\OS2\MOUSE.SYS o If the mouse is set on 3 button mode or Mouse Systems mode, use the the Type 2 configuration. DEVICE=C:\OS2\MDOS\VMOUSE.SYS DEVICE=C:\OS2\POINTDD.SYS DEVICE=C:\OS2\PCLOGIC.SYS SERIAL=COMx DEVICE=C:\OS2\MOUSE.SYS TYPE=PCLOGIC$ ( where 'x' is the COM port number. Either 1 or 2) ═══ 7.1.4. Type 4 CONFIG.SYS Statements ═══ These are the statements which are needed in the CONFIG.SYS file for the IBM 8516 Touch Screen. This device is only supported on Family 2 machines (Micro Channel Bus). DEVICE=C:\OS2\POINTDD.SYS DEVICE=C:\OS2\MDOS\VMOUSE.SYS DEVICE=C:\OS2\MDOS\VTOUCH.SYS DEVICE=C:\OS2\PDITOU02.SYS CODE=C:\TOUC021D.BIN INIT=C:\TOUCH.INI DEVICE=C:\OS2\TOUCH.SYS TYPE=PDITOU$ RUN=C:\OS2\CALIBRAT.EXE -C C:\CALIBRAT.DAT DEVICE=C:\OS2\MOUSE.SYS TYPE=PDIMOU$ ═══ 7.2. Pointing Devices Incompatible with OS/2 ═══ The following have been tested or confirmed by IBM to be incompatible with OS/2 2.x. They will likely need their own driver to operate with OS/2, which will be up to the manufacturer. Note: This list is not complete. ┌────────────────────┬────────┬────────┬────────┐ │Description │Type │Model # │Buttons │ ├────────────────────┼────────┼────────┼────────┤ │Kensington │Bus │62368 │N/A │ │Serial/Bus card as │ │ │ │ │bus card │ │ │ │ ├────────────────────┼────────┼────────┼────────┤ │Mouse Systems │Bus │903573-0│N/A │ │Serial/Bus card as │ │ │ │ │bus card │ │ │ │ ├────────────────────┼────────┼────────┼────────┤ │Prohance Power Mouse│Serial │N/A │40 │ │100 │ │ │ │ ├────────────────────┼────────┼────────┼────────┤ │Kurta Digitizing │Serial/B│N/A │4 │ │Tablet ( all models │ │ │ │ │) │ │ │ │ ├────────────────────┼────────┼────────┼────────┤ │Summagraphics │Serial/B│N/A │4 │ │Digitizing Tablet │ │ │ │ │(all models) │ │ │ │ └────────────────────┴────────┴────────┴────────┘ Note: IBM Touch Screens are not supported on family one machines Note: IBM 3-button mice operate the same as a Logitech mouse. ═══ 8. COMMON PROBLEMS & SOLUTIONS ═══ The following sections describe common mouse problems and solutions which have been discovered since the general announcement release of OS/2 2.0. This information is chronological by section, in that it starts with version 2.0, then has a service pak I section, and version 2.1. Just because the problem you are looking at is in a later version, does not mean that the solution from a previous section will not apply. ═══ 8.1. No mouse pointer or movement ═══ o Problem: No mouse pointer movement or no mouse pointer. An error is received upon boot up: SYS1201 VMOUSE.SYS not installed... o Explanation: This means that the MOUSE.SYS mouse driver was installed, but could not find a pointing device on the system, thus the virtual mouse driver for DOS VDM's "VMOUSE.SYS" was not installed. If it can not find a connected mouse, then it will not install VMOUSE.SYS (It does not mean that vmouse.sys was not found as the error implies). Either the install program could not correctly determine what type of mouse it was, or could not determine that a mouse was indeed present. o Resolution(s): This problem can be due to one of the following: 1. An unsupported type of mouse. Check to see if there are any dip switches on the mouse. Some mice have setable switches that put it into MicroSoft Mouse emulation mode. Also some mice have switches for either 2 or 3 button mode. Switch must be in two button mode. 2. Ask the customer what mouse driver was being used in DOS. If it is not the MOUSE.COM provided by DOS, then the mouse may be operating in a proprietary mode. If this is a dual boot machine, make sure the user is NOT loading the DOS MOUSE.SYS or DOS Device Dependant drivers. 3. If the user had mouse support during the graphical install portion of the installation process, then he/she probably changed the mouse driver/port that OS/2 had already chosen. Have the user run the Selective Install program found in the OS/2 System/System Setup folder and choose a different driver. 4. An interrupt conflict. Check the interrupts (use FI 863 as a guide). On an AT bus system, a serial mouse will only install on COM1 and COM2, and only if COM1 and COM2 are at the standard I/O addresses and IRQs: COM1= 3F8, IRQ4 and COM2= 2F8, IRQ3. See "OS/2 2.x And Serial Communications" (see REFERENCES) and InfoAPAR II06091 for a detailed review of Interrupts and OS/2. 5. A bus mouse that is not being detected. See below. ═══ 8.2. A bus mouse won't install ═══ o Problem: A bus mouse won't install. o Explanation: There are a myriad of reasons as to why a bus card won't install, ranging from incompatibility to IRQ conflicts. Work through the possible solutions below. o Possible Solution(s): This may be due to one of the following: 1. Bus mouse cards which have setable interrupts on the card. These usually are set at interrupt 2 which is often either a system interrupt, or on some systems is re-mapped to irq 9. set the interrupt to irq 5 (this is only if they do not have a second printer on lpt2). this should solve problem. If they have a second printer on lpt2 then they are out of luck since most cards only give the choices of 2-5, and 3 and 4 are reserved for com1 and com2. 2. Some bus mouse connections use IRQ0 which is the same as that used by the system timer. This is common when the mouse port is on the motherboard. A serial connection adapter can be used to get around this (ie. using the mouse as a serial mouse versus in the mouse port). 3. The MS Bus Mouse and the MS Inport Mouse (Grey Button) require a special card that only works on an AT style bus. This has IRQ jumper settings for 2-5. use IRQ5 when possible. 4. There is a problem with the autodetection system and Mouse Systems Serial/Bus card. This results in the system not "seeing" the mouse at install and thus it will not work. This is being looked at currently, and seems to be due to the card address. This may require its own special driver. The card can be used as a serial card using the standard addresses for COM1 : COM2. Most of their mice conform to the Microsoft standard, and thus can be used without the card in a standard 9-pin serial port. They will need only the mouse.sys line in the config.sys file. 5. Some Kensington Expert Bus Mice are not working, including the Kensington Expert Mouse Trackball. The mouse card is plugged into the bus and set for IRQ 10 and address 0338. We are currently working with Kensington Microware to resolve this problem. ═══ 8.3. Hewlett Packard HIL mouse will not work with OS/2. ═══ o Problem: Hewlett Packard HIL mouse will not work with OS/2. o Explanation: The HP mouse will not work with OS/2 without its own drivers. HP provides HILMOU.SYS and NOEXBIOS.SYS device drivers. Below is the instructions for adding support for the Hewlett Packard HIL mouse. This mouse has its own unique connector which looks similar to a phone jack. o Solution: Customers should go to their dealer for the diskette that contains HP mouse support. Customers may also access the files on Compuserve by typing "COMPUSERV GO HP". As a last resort they can call HP customer support (HP has asked us to refer them to their dealer first). HP Customer Service number is 1- 800-752-0900. Customers can use SELECTIVE INSTALL, and choose the OTHER POINTING DEVICE selection. This should prompt you for to insert a disk with the drivers into the drive and install the drivers with appropriate statements into the config.sys. If this does not work, then follow the steps below. Directions for installing a Hewlett Packard mouse and drivers. 1. Select PS/2 mouse during system installation at the Pointing Device selection panel. 2. Copy HILMOU.SYS and NOEXBIOS.SYS to C:\OS2 (these are supplied by HP) 3. Update the CONFIG.SYS file with the following statements in the order shown: add DEVICE=C:\OS2\NOEXBIOS.SYS add DEVICE=C:\OS2\HILMOU.SYS modify DEVICE=C:\OS2\MOUSE.SYS TYPE=HILMOU$ (This line should already be in the CONFIG.SYS but will need the TYPE=... added ) 4. Reboot the system. ═══ 8.4. Mouse pointer will not move ═══ o Problem: Get a pointer on the screen, but when mouse is moved there is no movement or response from the pointer on the screen. o Explanation: This is a classic symptom of an interrupt conflict. The mouse was installed (thus the pointer on the screen), but another device has stolen the interrupt away from the mouse so when it is moved nothing happens. o Solution: You will need to figure out what is causing the conflict. If it is a bus card, there should be settings on the card to allow you to choose other IRQs. See section IX for standard system interrupt mappings. This will help in deciding a free interrupt to use. IRQ5 is often a safe choice if there is not a second printer on LPT2. If the mouse is in a serial port, check the other devices on the machine. Modem cards, Tape backup devices, Soundblaster cards, and other ASYNCH communications devices may have preset interrupts on their cards which conflict with the standard IRQs assigned to COM1 and COM2. As a last resort, you may have to ask them to remove all the other cards on the system one at a time to see who the culprit is. Note: For further assistance with interrupt problems, refer to the "OS/2 2.x and Serial Communications" document (see REFERENCES). ═══ 8.5. IBM mouse is not working, or is giving "wild mouse" or intermittent behavior. ═══ o Problem: IBM mouse is not working, or is giving "wild mouse" or intermittent behavior. o Explanation: Some of the IBM mice with a black roller ball that are manufactured in Taiwan have hardware specification deficiencies. o Solution: Replace mouse with a grey ball IBM mouse, or any MS compatible mouse. ═══ 8.6. On a 3 button mouse, only 2 of the buttons will work. ═══ o Problem: On a 3 button mouse, only 2 of the buttons will work. o Explanation: The OS/2 mouse driver only supports 2 button mice, thus on a 3 button mouse only two of the buttons will function. Effectively the 3 button mouse acts as a 2 button type. o Solution: Contact the manufacturer to see if they have or are currently developing their own drivers for OS/2 to allow three button functionality. Otherwise for the time being use as a 2 button mouse. ═══ 8.7. Prohance Power Mouse 100 will not work with OS/2. ═══ o Problem: Prohance Power Mouse 100 will not work with OS/2. o Explanation: This is a programmable mouse with over 40 buttons on it, which allows it to emulate not only all mouse functions, but also all keyboard functions. It can be tailored so that a specific button will perform a certain operation, based on which application is currently running. This of course requires its own special set of drivers and software programs. This mouse is not Microsoft compatible. o Solution: At this time Prohance has no intention of developing for OS/2. The best advice you can give to customer is to write/call Prohance and put pressure on them to develop for OS/2. In the mean time advise them to get a standard serial mouse to enable them to do work on their system. ═══ 8.8. Unattended start mode resident on MOD 90 and 95 disables mouse in workplace shell. ═══ o Problem: Unattended start mode resident on MOD 90 and 95 disables mouse in workplace shell. o Explanation: If the unattended start mode is set on a mod 90 or 95 and the password is not typed in prior to the boot manager's time out, the system will come up, but an error message comes up from config.sys "sys1201 C:\os2\mdos\vmouse.sys device driver in that path was not installed...... ignored,press enter,". If the password is then typed in, the system will continue to come up but the mouse is totally disabled in the workplace shell. If the unattended start mode password is typed prior to the boot manager 's time out, then the mouse works correctly. Problem Summary: NOTE: This problem is a permanent restriction. The 8042 chip controller handles both the keyboard and mouse ports. By setting a power-on password, I/O is blocked from this chip. User key sequences are internally buffered and compared against the password stored in CMOS. Once a match is made, the keyboard and mouse ports are again enabled. The MOUSE.SYS and any other mouse driver needs to access this port in order to load. When it is locked, it cannot. Unfortunately, this feature is not of much use for systems with mice. Both the mouse and the keyboard ports are locked by the 8042 controller chip. o Solution: Make sure you enter the unattended start mode prior to bootup manager's time out. ═══ 8.9. When in net server mode the mouse device driver will not load. You will get a message during init ═══ o Problem: When in net server mode the mouse device driver will not load. You will get a message during init time stating this and prompting you to hit ENTER to continue. Since keyboard input is locked out you will be stuck. o Solution: There are two options available. Either take out your mouse support lines from config.sys or add the line below to config.sys PAUSEONERROR=NO The first option is better if you always start the system in net server mode and the second is better if you don't. If you add the line above to config.sys and the system still hangs then you have uncovered a bug in the mouse device driver which we should look into. ═══ 8.10. The mouse will not work after a resume from power down on L40SX or other laptop. ═══ o Problem: The mouse will not work after a resume from power down on L40SX or other laptop. o Explanation: This is due to a problem with the 8042 controller chip on the PDI port. This is fixed in version 2.1 Serial, bus, and inport mice will still function after a power down/ resume as they do not access the system through the 8042 controller chip. o Solution: User must upgrade to version 2.1. The only other solution is to switch to a serial, bus, or inport mouse, as they are not affected by the 8042 controller chip. ═══ 8.11. A serial mouse won't work even though the IRQs check out. ═══ o Problem: A serial mouse won't work even though the IRQs check out. Additional Problem Determination: 1. If the mouse is attached to COM3 or COM4, it will not work at this time. We only support attachment to COM1 and COM2. 2. If the mouse is attached to COM1 or COM2, verify that the com port is at the standard I/O address and IRQ. 3. Issue a MODE COMx (where x is 1 or 2) from an OS/2 or DOS command prompt. This is a test of the COM ports: a. If it reports that the port (the one the mouse is attached to) is NOT available, then MOUSE.SYS is LOADED. This means that the drivers are correct; don't change the CONFIG.SYS statements. b. If it reports the baud rate and all the other COM port parameters, then MOUSE.SYS did not recognize the mouse and did NOT Load. See InfoApar II06079 for correct driver. Note: If com problem suspected consult "OS/2 2.x and Serial Communications" document (see REFERENCES) steps to resolve problem. ═══ 8.12. Mouse Systems bus mice will not work under OS/2 at all, including during install. ═══ o Problem: Mouse Systems bus mice will not work under OS/2 at all, including during install. o Explanation: The Mouse Systems Serial/Bus card (MSC 903573-001) will not work with OS/2 when configured as a bus card, at this point in time. This seems to be due to an addressing problem. It is likely that it will require either it's own driver, or mouse.sys to be modified for it to work. The card will work as a serial card configured for COM1 OR 2 however, and thus for now should be used as such if possible. o Solution: Card should be removed, and reconfigure it as COM1 or 2 and re-install it as a serial pointing device. Most of the Mouse Systems mice will operate with the Microsoft standard, and can be used as serial mice with or without the card. They come with a DB-9 connector, but if the customer only has a 25 pin serial port on machine, they will need an adapter. If the mouse has a 2-button/3-button switch, it must be set to the 2-button position. Install as a serial pointing device. If mouse still does not work, it may be that it is one of their older models which do not operate with the MS standard INT33 interrupt. Check the list in this document or have customer call Mouse Systems. ═══ 8.13. Kensington bus mice will not work under OS/2 at all, including during install. ═══ o Problem: Kensington bus mice will not work under OS/2 at all, including during install. o Explanation: The Kensington Serial/Bus card will not work with OS/2 when configured as a bus card, at this point in time. This seems to be due to an addressing problem similar to the Mouse Systems problem. The card will work as a serial card however, and thus for now should be used as such if possible. Kensington has a driver for OS/2 in beta test as of this writing, and it should be available soon. This driver will allow the bus card to work with OS/2. o Solution: Card should be removed, and reconfigure it as COM1 or 2 and re-install it as a serial pointing device. Kensington mice will operate with the Microsoft standard, and can be used as a serial mouse or in the PDI port with or without the card. They come with a DB-9 connector, but if the customer only has a 25 pin port on machine, they will need an adapter. Note that there are dip switches on these trackballs which should be set to click lock positions as explained in their instructions. Customer should contact Kensington to see when their mouse driver will be available. ═══ 8.14. Logitech Mouse doesn't function under OS/2 when installed with the Logitech driver. ═══ o Problem: Logitech Mouse doesn't function under OS/2 when installed with the Logitech driver. o Explanation: Most Logitech mice emulate Microsoft mice and use the PS/2 Style Pointing Device selection. The system should auto detect most of the more recent Logitech models, and install them as such. o Solution: The CONFIG.SYS should contain the following statements: DEVICE=C:\OS2\MDOS\VMOUSE.SYS DEVICE=C:\OS2\POINTDD.SYS DEVICE=C:\OS2\MOUSE.SYS (do not specify TYPE=...) When a user selects an incorrect mouse, (Logitech serial, for example), then goes back via selective install and changes the selection (to PS/2 pointing device, for example), the statement DEVICE=C:\OS2\PCLOGIC.SYS sometimes may be left in the CONFIG.SYS and the mouse will not work. The user must edit CONFIG.SYS and remove the offending statement by hand, leaving only the MOUSE.SYS and POINTDD.SYS statements in CONFIG.SYS. Note: see section VIII LOGITECH POINTING DEVICES : OS/2 for further info. ═══ 8.15. After performing dual boot to DOS, Logitech mouse does not work. ═══ o Problem: After performing dual boot to DOS, Logitech mouse does not work. o Explanation: Some Logitech mice have "memory" that remembers the mode it was in previously. Often while in DOS, these will be in "Mouse Systems Protocol" (5 byte, 1200 baud) and need to be returned to "Microsoft Protocol". o Solution: Before performing the dual boot, open a DOS window or full screen and type MOUSE PC. (If the mouse is in COM2, type MOUSE 2 PC.) You can also perform a cold boot if this command does not work, this should allow the mouse to reset. Note: must be using the mouse.com that came with the mouse (primarily Logitech), or the command will not work. ═══ 8.16. No mouse pointer in a VMB (Virtual Machine Boot). ═══ o Problem: No mouse pointer in a VMB (Virtual Machine Boot). o Explanation: The 80386 virtual 8086 mode supports execution of 8086 or 8088 programs in a protected-mode environment. Virtual 8086 mode enables system software to emulate an 8086 environment with a "virtual Machine. the 80386 hardware provides an encapsulated virtual 8086 environment, while system software controls the external interfaces of the virtual machine, such as I/O devices and interrupts. The booted DOS in a VMB session receives mouse support services from its VDM environment ( assuming default settings). DOS should not load its own mouse driver, it may cause an error in the VDM. O S/2 provides alternative 'stub' drivers to avoid this problem. The mouse driver is call MOUSE.COM and is located in the OS2\MDOS subdirectory. o Solution: Make sure that they are using the MOUSE.COM provided in OS2\MDOS subdirectory. ═══ 8.17. The mouse gets out of sync on a 50 MHz Systems (AT bus). ═══ o Problem: The mouse gets out of sync on a 50 MHz Systems (AT bus). o Explanation: There have been some intermittent problems with AT-style bus machines with a mouse. The mouse can get out of synch. Input will function through the keyboard and the mouse, but it is recommended to shutdown the system and restart to "resynch" the mouse. o Solution: Shutdown system to resynch the mouse. ═══ 8.18. The mouse pointer suddenly zips over to the side of the screen and hangs there, no longer ═══ o Problem: The mouse pointer suddenly zips over to the side of the screen and hangs there, no longer responding to any mouse movements. Sometimes windows will open and close when mouse is moved, or pointer will only move up and down the side. This has been given the dubious moniker of "Wild Mouse". In most cases, a cold boot has been the only remedy. o Explanation: This is caused by a hardware glitch and cannot be prevented from happening, but can be recovered from without a cold boot being required by using the newest version of the mouse driver (dated 9/9/92 or later), which is also in the service pack. o Solution: Obtain 9/9/92 or later mouse.sys. This will be in the service pack. ═══ 8.19. The PS/2 Mouse on a PS/2 machine is responding too slow. ═══ o Problem: The PS/2 Mouse on a PS/2 machine is responding too slow. Solution: Obtain 9/9/92 or later mouse.sys. This will be in the service pack. ═══ 8.20. Clix mouse (Genius Clix) will not work. ═══ o Problem: Clix mouse (Genius Clix) will not work. o Solution: The Clix mouse is a Genius clone mouse and needs the following lines inserted into the CONFIG.SYS file DEVICE=C:\OS2\PCLOGIC.SYS SERIAL=COM1 DEVICE=C:\OS2\MOUSE.SYS TYPE=PCLOGIC$ After reboot the mouse should work. ═══ 8.21. Clix 3-button MS-compatible mouse not being recognized by OS/2. Get SYS1201 ERROR. ═══ o Problem: Clix 3-button MS-compatible mouse not being recognized by OS/2. Get SYS1201 ERROR. o Explanation: This Clix mouse is a 3 button mouse. It has a switch to make it work as a 2 or 3 button mouse. The 2-button state is Microsoft compatible, the 3 button state is non-Microsoft compatible. o Solution: Once switch is changed to the 2-button setting mouse should work fine. You may need to reboot for this to take effect. ═══ 8.22. Toshiba Docking Station exhibits "Wild Mouse" symptoms. ═══ o Problem: Toshiba Docking Station exhibits "Wild Mouse" symptoms. o Explanation: The Toshiba Docking Station allows a portable to be connected to a main frame or LAN. The mouse must be unplugged from the back of the portable and plugged into the docking station mouse port. The Docking station will exhibit the wild mouse symptoms when mouse is unplugged and replugged back into the docking station port., because this allows the mouse byte information to get out of synch. This is known as a "hot plug mouse" problem. o Solution: The most current mouse driver, dated 9/9/92 (or later), will allow this particular version of the wild mouse behavior to reset. This driver is in the service pack. A future release of the mouse driver will allow all hot plug situations to exist with no errant behavior (ie. you will be able to unplug your mouse and plug it back in with out having to reboot in order to regain the mouse). ═══ 8.23. When using touch screen device cannot get mouse to work, or get wild mouse type behavior. ═══ o Problem: When using touch screen device cannot get mouse to work, or get wild mouse type behavior. o Explanation: This is due to a hardware compatibility problem and is a permanent restriction. Since there is no real standard to which mouse hardware is written, the data rates and protocols vary widely and is really up to the manufacturer. The IBM touch screens are designed to work with the IBM grey ball mice only. The 8516/Touch Select drives its mouse port slightly differently that the planar does. The planar keyboard/mouse (8042) controller sits with both the keyboard and the mouse enabled, ready to accept input from either. When one device starts to give a report, it disables the other by inhibiting it and driving the clock line low. Generally speaking, although it can accept the input from only one device at a time, due to the low data rates and small amount of processing of the data (just reading in the bytes, checking parity and putting them in an output register and raising an interrupt line) data reports are never lost from either device. With the 8516, things are a lot different, as the same controller handling the mouse input is also doing all the signal processing and calculations to convert the strain gauge values to x,y,z reports. The end result is that the reading of the mouse port is at the end of a priority list, which mainly consists of things that must be done to handle the touch screen part. Only when there is no higher priority touch screen activity, does it go and poll the mouse port for data. To keep the mouse quiet, it keeps it inhibited by driving the clock line low. So when it has finished the touch chores, it de-inhibits the mouse by raising the clock line, and then waits for the mouse to give a report if it has one. It only waits so long, before being called back to doing the touch screen processing which is done off a timer interrupt. The polling thus happens periodically but it is done frequently enough to cope with all but the highest mouse report rate. Where it fails though, is when the mouse is not quick enough off the mark to notice the clock line going high and give its report in time before the line is raised again as the controller handles the touch screen. With the black ball mouse, the 'window of opportunity' was extended sufficiently to allow it work. At the time, we thought that this was the same problem with the Microsoft Mouse, as it seemed to exhibit the same behavior, but this was a red herring and the real reason was that the spare two bits in byte 0 of its report were set differently from the IBM mice. o Solution: Use an IBM grey ball mouse. ═══ 8.24. Chicony keyboard w/built in trackball. Trackball not working or get SYS1201 error. ═══ o Problem: Chicony keyboard w/built in trackball. Trackball not working or get SYS1201 error. o Explanation: The Chicony keyboard w/ trackball comes with software that allows you to set the mouse mode. The mouse may be set in a mode which is not compatible with OS/2. o Solution: Use the Chicony setup program to set the mouse part of the keyboard to a Mouse Systems type device. Then edit the CONFIG.SYS file in the root directory as shown below; 1. Change the line that reads DEVICE=C:\OS2\MOUSE.SYS to read DEVICE=C:\OS2\MOUSE.SYS TYPE=PCLOGIC$ 2. Just above this line add the following line DEVICE=C:\OS2\PCLOGIC.SYS SERIAL=COMx (where x is 1 or 2) 3. Save CONFIG.SYS file, and reboot computer. ═══ 8.25. When mouse set as left handed on desktop, will not be set in Win-OS/2, or if set both on desktop ═══ o Problem: When mouse set as left handed on desktop, will not be set in Win-OS/2, or if set both on desktop and in Win-OS2 and a seamless windows app is run on desktop, mouse reverts to right handed mouse. o Explanation: In both the GA and Service Pack releases of OS/2, when the mouse is set as lefthanded on the desktop it does not change it automatically in Win-OS2. Once it is changed, if a seamless windows app is run on the OS2 desktop, it is changed back to right handed by the desktop settings because it does not know that it has already been toggled to left handed by the WIN-OS2 settings. o Solution: This is fixed in 2.1, but for now there is nothing that can be done. If the user chooses to run all windows applications seamlessly on the desktop, then if they DO NOT set mouse as left handed in WIN- OS2, it will be lefthanded when running in the seamless window. ═══ 8.26. Mouse plugged into PDI mouse port on non IBM machines does not work or exhibits intermittent or ═══ o Problem: Mouse plugged into PDI mouse port on non IBM machines does not work or exhibits intermittent or flaky behaviour. o Explanation: The Mylex MNE-486-33 Motherboard among others, has a compatibility issue at their end (ie: they use a 8242 chip as the keyboard, mouse port controller). Any of the mouse ports that use a non 8042 chip will not always respond properly to mouse input, or the mouse driver may not even recognize the there is a mouse on the system. Texas Instruments and Packard Bell also use a non-8042 mouse port controller on some of their machines. o Solution: Use a serial or bus mouse. In the case of Texas Instruments, they have developed their own OS/2 mouse driver. For Pacakard Bell see the section titled same. ═══ 8.27. The OS/2 2.0 Toolkit Device Driver Documentation Incorrect ═══ o Problem: The OS/2 2.0 Toolkit documentation, specifically the manual "OS/2 2.0 Physical Device Driver Reference" was not changed to reflect the code change to touch display support. o Explanation: The mouse IDC, Process_Absolute, has been changed in OS/2 2.0 because a defect was raised by the IBM Touch Display support added to 2.0. The change was to remove the function where the MOUSE.SYS device driver would check the movement of the mouse pointer against the button mask that was passed in and change that mask if there was a discrepancy. This was deemed in error since there are occasions where the device dependent driver may want to pass these bogus values up the chain to running applications. The OS/2 2.0 Toolkit documentation, specifically the manual " OS/2 2.0 Physical Device Driver Reference" was not changed to reflect the code change. In chapter12, Physical Mouse Device Driver in the Mouse IDC section, on page 12-3 there is a reference to the "EVENT" field that section, on page 12-3 there is a reference to the "EVENT" field that should be changed. o Solution: Remove / Ignore the following sentence. The event field should never indicate that motion was associated with the event. MOUSE$ determines if motion occurs. ═══ 8.28. In AUTOCAD, ATI mouse responds differently than other 3 button mice. ═══ o Problem: In AUTOCAD, ATI mouse responds differently than other 3 button mice. o Explanation: Logitech serial mouse uses buttons 1 : 2 normally on desktop, but in autocad logitech uses all 3 buttons. In autocad, uses button 3 to call up the popup menu . The ATI 3 button mouse has #2 button non-functional on desktop, and button 2 stays non- functional even in autocad. can not get popup menu with #2 button (or any other for that matter). o Solution: If shift key is held down and hit button 2, then can get the popup menu with no problem. ═══ 8.29. Outside vendor writes a pointing device driver but mouse won't work and gets no other errors. ═══ o Problem: Outside vendor writes a pointing device driver but mouse won't work and gets no other errors. o Explanation: Prodigy wrote their own cad driver for summagraphics, but the pointer did not move. problem was that Workplace shell asks what type device is attached, and this device driver returned unkown. So got the pointer but it didn't move. Desktop basically said since i don't know what kind of mouse it is, it won't respond to mouse input. o Solution: Device driver must return what type of device it is. ═══ 8.30. Right mouse button will not work on desktop. May not drag icons or bring up menu. ═══ o Problem: Right mouse button will not work on desktop. May not drag icons or bring up menu. o Explanation: Many times this is due to currupted .INI system file(s). o Solution: A reformat/reinstall has been known to fix this, but this is a drastic move which should be avioded except as a last resort. A better way to fix is to use the MAKEINI command or even easier is to just boot from a dos disk or os/2 install disks, and then copy over the OS2.INI and OS2SYS.INI from the C:\OS2\INSTALL directory to the C:\OS2 directory. This will usually solve the problem. ═══ 8.31. System with any microsoft mouse stops with a 0X when try to bring up windows either from a ═══ o Problem: System with any microsoft mouse stops with a 0X when try to bring up windows either from a desktop object or from a full screen. (see below) ═══ 8.32. System exhibits any number of unusual behaviors after customer claims to have installed the ═══ o Problem: System exhibits any number of unusual behaviors after customer claims to have installed the Microsoft mouse drivers that came with their mouse. o Explanation: system has a contaminated dos/windows device driver and possibly the wrong system mouse driver as well, due to using the install program on the disk which accompanies the Microsoft mouse. The 0X error refers to the SYSTEM.INI file. If this has been altered due to the install, it will be found that the system will attempt to load a mouse.sys from the os2\mdos directory that is not there. o Solution: There may be a lot involved in recovering from this mess. The install program may copy the microsoft mouse.sys file over the os/2 mouse.sys mouse driver. Check the file dates and sizes with the ones on the install disk and on os/2's sytem diskettes. ═══ 9. PROBLEMS AFTER SERVICE PACK 1 ═══ ═══ 9.1. Receive Error SYS1719 in C:\OS2\MDOS\V8514A.SYS during boot up after installing service ═══ o Problem: Receive Error SYS1719 in C:\OS2\MDOS\V8514A.SYS during boot up after installing service pack o Explanation: After installing the service pack receive the message: SYS1719 on C:\os2\mdos\v8514a.sys This DID not occur prior to the service pack. Remarking statement in the config.sys out seemed to work, The V8514A.SYS is 8997 bytes in size dated 10/16/92. o Solution: The problem was apparently that the v8514a.sys in my original config.sys and the service pack must have inserted the vvga.sys vwin.sys and a v8514a.sys at the end of the config.sys without checking for any of these higher up in the file. This may have happened during the Service Pack that was shipped internally last week and could have been fixed in the 'real' SP. Check for duplicates of these statements in the CONFIG.SYS after service pack install, and remove them. ═══ 9.2. Flaky mouse pointer in Win-OS2 applications with an 8514 display. Especially noticeable with the ═══ o Problem: Flaky mouse pointer in Win-OS2 applications with an 8514 display. Especially noticeable with the ATI 8514 card. o Explanation: The use of the 8514 display means user can't have seamless window sessions. The mouse pointer is only flaky in a Window app (e.g. Excel) run in full screen mode. What is occurring is likely due to interrupts either being lost or not interpreted fast enough and what results is jerky movement of the mouse pointer on the screen relative to the actual mouse movement. The pointer is always catching up to the mouse even when it is moved slowly. o Solution: Mouse Exclusive Access does help significantly but does not completely solve the problem of the disappearing pointer. It will not jump around at all but will occasionally (a lot less) disappear. Changing Idle-Sensitivity to 100 and Idle-Seconds to 20 seems to solve the problem, but this is not an ideal solution. This problem is being looked at by development. A temporary fix that seems to work for the ATI ULTRA card is as follows: 1. From the ati 1.3 video device drivers diskette copy the windows 3.0 device driver called ULTRA.DRV to the OS2\MDOS\WINOS2\SYSTEM subdirectory. 2. From the OS2\MDOS\WINOS2 subdirectory type E SYSTEM.INI 3. Change DISPLAY.DRV=8514.DRV to DISPLAY.DRV=ULTRA.DRV 4. Save the changes. 5. From settings set the 8414 trap to off and set video notification on. 6. Reboot and test. Note: using this device driver makes it so user is unable to use alt/esc in winos2. ═══ 9.3. Using selective install to change mouse type or port (serial vs pdi), causes loss of mouse. ═══ o Problem: Using selective install to change mouse type or port (serial vs pdi), causes loss of mouse. o Explanation: When trying to reinstall a mouse, the selective install of service pack seems to leave the correct statements in CONFIG.SYS (not confirmed by testing), but the mouse will not work. o Solution: A complete reinstall with selection of the correct mouse driver seems to cure this problem. ═══ 9.4. There are various symptoms of funny mouse behavior on the desktop, such as jerky pointer ═══ o Problem: There are various symptoms of funny mouse behavior on the desktop, such as jerky pointer movement, right button not bringing up menu all the time, pointer disappearing, etc. o Explanation: There were changes made to the Presentation Manager interface in service pack which seem to have affected how the mouse events are interpreted while on the desktop. The events are picked up by MOUSE.SYS, but as they are passed on either they get lost or misinterpreted. o Solution: If there was not some specific need for the fixes in service pack, go back to the GA release of os/2 and wait for the next full version release. This problem should be fixed by then. ═══ 9.5. Size of pointer is too large or too small. Especially on portables pointer may seem large. ═══ o Problem: Size of pointer is too large or too small. Especially on portables pointer may seem large. o Explanation: This exists because people asked for a larger pointer on the plasma screens, but some like the smaller size. will work on any display though.size of pointer is controlled by video. there are two command files LARGE.CMD : SMALL.CMD which will change pointer size on service pack machines o Solution: After service pack, mouse pointer size can be set to large or small by using two command files LARGE.CMD" and "SMALL.CMD". these toggle a switch in the system ini file, and then must reboot for it to take effect. These may have to be sent to customer. ═══ 9.6. Some 3-button mice exhibit "wild mouse" behavior that occurs when non-active button is hit. ═══ o Problem: Some 3-button mice exhibit "wild mouse" behavior that occurs when non-active button is hit. o Explanation: Button is not completely disabled, thus when button is hit it sends unexpected byte packets which cause mouse driver to go out of sync on read of byte packets. o Solution: There is a new option called RELAXED which corrects this behavior. It will be available in release 2.1 and is documented in the on line help. Basically the word RELAXED is added to the MOUSE.SYS line in the CONFIG.SYS file, and then reboot. Note that this may also be in service pack 2. Check the on line help. ═══ 10. VERSION 2.1 PROBLEMS ═══ ═══ 10.1. Receive SYS1201 ERROR upon first boot after install of 2.1 ═══ o Problem: Receive SYS1201 ERROR upon first boot after install of 2.1 over existing operating system (ie. DOS, OS/2 1.x or 2.x, or Windows). o Explanation: If there is a previous mouse driver on the system with the name MOUSE.SYS, the install program finds it and copies it into the \OS2 directory instead of the OS/2 2.1 MOUSE.SYS driver from the install disks. This is an error in the install program, not the mouse driver. o Solution: The following steps should be followed to verify that the correct mouse driver is loaded. 1. Have the customer review the CONFIG.SYS file (i.e. E.EXE CONFIG.SYS) and verify that the DEVICE= statment points to MOUSE.SYS in the x:\OS2 directory (where x: is the installed drive and is usually 'c'). 2. Have the customer SEARCH for MOUSE.COM. This should NOT exist in the CONFIG.SYS file for OS/2. 3. Have the customer give you the DATE and SIZE of the MOUSE.SYS driver which is located in the x:\OS2 directory (x: being the installed disk drive letter which is usually 'c'). 4. The MOUSE.SYS should have a date of 4-26-93 and a file size of 15053 bytes. If this is not the case, have the customer rename the current MOUSE.SYS and copy the MOUSE.SYS from DISK 1 of the installation set for OS/2 2.1. 5. If the customer installed from CD-ROM and gets the SYS1201 VMOUSE NOT INSTALLED or MOUSE DRIVER NOT INSTALLED, have the customer copy the MOUSE.SYS driver from DISK 1 of the installation set for OS/2 2.1. EVEN IF THE DATE AND FILE SIZE MATCH, IF THE CUSTOMER INSTALLS FROM CD-ROM, HAVE THE CUSTOMER FOLLOW THIS PROCEDURE. 6. The APAR for this problem is PJ08916. ═══ 10.2. ERROR SYS1201 VMOUSE NOT INSTALLED at boot up ═══ o Problem: Receive ERROR SYS1201 VMOUSE NOT INSTALLED for mouse in a serial port at boot up. May not occur all the time. o Explanation: Due to some new features added into the mouse driver, on certain hardware mouse combinations, will grab the com-port as it sets up for the mouse, but it won't let go. this then prevents the loading of the correct code for that mouse, and thus the VMOUSE.SYS driver will not load and the error occurs. o Solution: First see previous panel to determine that the correct version 2.1 mouse.sys system mouse driver was installed. If not follow the steps in that panel to correct the problem. If it is the correct 2.1 driver, see next paragraph. In some cases simply unplugging and replugging the mouse will allow the port to reset. If not try a warm boot ( CTL-ALT-DEL ). If this does not work and they have a previous version of OS/2 they can copy that mouse driver into the \OS2 directory and use that one instead (save the other just in case). The apar for this problem is PJ08908. ═══ 10.3. 3-button mouse does not work as left handed ═══ o Problem: 3-button mouse does not work correctly as left handed on desktop. o Explanation: Originally OS/2 only supported 2-button mice. When the 3-button mouse support was added, it was decided that the desired mappings of the left/ middle/right buttons would be 1-3-2 meaning that the left button would be the same as on the 2-button mice, and the right button would be the same as the right button on the 2-button mice, and the middle button would be the extra button. This caused confusion with the button mappings of the workplace shell, as it was expecting the l/m/r order to be 1-2-3. The expected mapping should be 2-3-1 but what occurs is 3-1-2. o Solution: This is will be fixed in service pak II. The apar for this problem is PJ08854. ═══ 10.4. IBM 700 series (Thinkpad) mouse lost on resume from suspend. ═══ o Problem: IBM 700 Series (Thinkpad) pointing stick control lost on resume from suspend. Note: On occasion the pointing stick will seem to work in every direction except the negative Y direction (towards bottom of screen). In this direction it will move as if through peanut butter, agonizingly slow. This is a symptom of the same problem. o Explanation: When a 700 series laptop is put into suspended mode (power saving mode), the pointing stick is powered down as well. When resuming to normal operations, there is a lag time while machine is cycled up. During this period the pointing stick is powered up and the 8042 mouse port chip is reset (the Trackpoint II pointing stick runs from this chip). If the pointing stick is moved (ie. move screen pointer) before power up is completed, data from the device is sent to the chip and it hoses the reset process and the interupt is lost. o Solution: 1. DO NOT MOVE THE MOUSE UNTIL THE BEEP SOUNDS, which signals resume is complete and all hardware enabled. At that point there will be no problem with the mouse. 2. If pointer has already been lost or is moving slow, hit the suspend button again and go through the resume cycle this time not touching stick until beep sounds. This will be fixed in Service Pak II. The apar for this problem is PJ08909. ═══ 10.5. PC MOUSE SYSTEMS mouse does not work ═══ o Problem: PC MOUSE SYSTEMS mouse does not work, even though MOUSE SYSTEMS driver was selected from mouse install panel. o Explanation: Some of the newer Mouse Systems mice use the Microsoft protocol. If they have a 2/3 button switch on the bottom, 2 is Microsoft protocol, and 3 is Mouse Systems protocol. Depending on which setting the button is on, will determine which mouse driver to install. Either setting will work with the correct driver. Some of the mice do not have the switch, and use the Microsoft protocol. The only way to be sure is to call Mouse Systems and ask them based on the model number on the bottom of the mouse. o Solution: Determine which protocol the mouse is using and install the correct driver, or edit the CONFIG.SYS file with the correct mouse statements. See Chapter 7 CONFIG.SYS Statements, for the correct statement information. ═══ 11. LOGITECH POINTING DEVICES AND OS/2 ═══ All Logitech pointing devices will work with version 2.0 of OS/2 provided proper installation options are chosen during the OS/2 system configuration. This following lists the pointing device and the steps to make it function properly. They have all been tested with OS/2, by the Logitech Corporation. ═══ 11.1. M-Series Serial Mice ═══ These include but are not limited to the following devices which run as Microsoft compatible devices o Mouseman Serial o Radio o Trackman Portable o Trackman II on serial port The proper selection for these devices is LOGITECH M-SERIES. During initial install for OS/2, the operating system finds and configures the system for the mouse correctly without user intervention. Thus you should not need to select a driver for the pointing device. Check the systems selection, the proper selection is the M-SERIES selection. When updating from No Pointing Device or other type of mouse, user should pick the Serial Pointing Device selection for version 2.0 and service pack, and the Logitech M-Series Mouse selection for version 2.1. Follow the prompts and identify the port mouse is on, with the choices being COM1 or COM2 (at this time OS/2 will not support a pointing device on COM3 or COM4). Continue with installation, inserting diskettes as requested. ═══ 11.2. C-Series Serial Mice ═══ These include but are not limited to the following devices which run as Mouse Systems compatible devices o C-7 o CC o CA o CE o TrackMan-1 on serial port The proper selection for these devices is LOGITECH C-SERIES. The initial OS/2 installation procedure will NOT find these devices and at the appropriate time during the installation, OS/2 will ask the user which device they would like to use. Select the LOGITECH SERIAL MOUSE and when asked, pick either COM1 or COM2. Complete the installation, turn off the computer, boot to OS/2, and the mouse will then be working. Note: On Dual Boot and Boot Manager When using OS/2's DUAL BOOT or BOOT MANAGER feature, it is important to note that the C-series mice, when used in DOS, are MM protocol and must be reset to the Mouse Systems protocol (5 Byte,1200 Baud) by typing MOUSE PC at the DOS command line and then issuing the command to return to os/2 and performing a warm boot. If for some reason this command does not work, then user can try the following either 1. unplug and replug mouse or 2. perform a cold boot to OS/2. The MOUSE PC command must be used with the Logitech MOUSE.COM under DOS. This command and the dual boot command can be combined into a one word batch file. ═══ 11.3. Bus & PS/2 Style Mice ═══ These include but are not limited to the following devices which run as Microsoft compatible devices o P7 o PA o PD on BUS card with correct IRQ SETTINGS o PS/2 models The proper selection for these devices is PS/2 STYLE POINTING DEVICE. Note: IRQ settings and bus cards. It is important that the IRQ setting on the bus mouse card be set to an available interrupt number. If you have a choice in the range 2-5, the only open IRQ is 5, and this is only true if you are not using LPT2 for a second printer (see section called IRQ Settings) ═══ 11.4. CONFIG.SYS Statements for Logitech Devices ═══ The lines needed for each type of pointing device are shown below. It is not absolutely necessary to run the selective install to change the system configuration for the mice. By changing the CONFIG.SYS file for os/2, the system can be re-configured for each type of pointing device. In every case there are some lines which DO NOT need to be changed, but still need to exist. These include: DEVICE=C:\OS2\MDOS\VMOUSE.SYS DEVICE=C:\OS2\POINTDD.SYS Lines that DO CHANGE follow for each specific type of mouse. o BUS and PS/2 TYPE: Will add the following if not already there. DEVICE=C:\OS2\MOUSE.SYS o M-Series Serial Mice: DEVICE=C:\OS2\MOUSE.SYS SERIAL=COMx (where x=1 or 2) o C-Series Serial Mice: DEVICE=C:\OS2\PCLOGIC.SYS SERIAL=COMx ( ? = 1 or 2 ) DEVICE=C:\OS2\MOUSE.SYS TYPE=PCLOGIC$ Known Logitech Model Numbers as they appear on the hardware (not complete!!!): Description Type Model Number CONFIG.SYS Buttons ------------------------------------------------------------------------------ Mouseman Serial M-MC13-DB9F Type 1 3 Trackman Serial T-CA1-9F Type 2 3 Trackman Serial T-CC2-9F Type 1 3 Series 9 PS/2 CE9-6MD Type 1 3 Series 9 Serial CC-93-9F Type 2 3 Series 2 PS/2 2-7S Type 1 2 In the config.sys statements, the assumption is that each contains the following statements: o Type 1 DEVICE=C:\OS2\MDOS\VMOUSE.SYS DEVICE=C:\OS2\POINTDD.SYS DEVICE=C:\OS2\MOUSE.SYS o Type 2 DEVICE=C:\OS2\MDOS\VMOUSE.SYS DEVICE=C:\OS2\POINTDD.SYS DEVICE=C:\OS2\PCLOGIC.SYS SERIAL=COMx ( where x is 1 or 2) DEVICE=C:\OS2\MOUSE.SYS TYPE=PCLOGIC$ ═══ 12. IRQ SETTINGS ═══ The descriptions reflect the usual assignments for the given hardware interupt. ┌──────────┬────────────────────────────────────────┐ │IRQ Level │Description of usage │ ├──────────┼────────────────────────────────────────┤ │IRQ0 │System Timer ( channel 0 ) │ ├──────────┼────────────────────────────────────────┤ │IRQ1 │Keyboard │ ├──────────┼────────────────────────────────────────┤ │IRQ2 │Secondary Interrupt Controller ( see │ │ │note below ) │ ├──────────┼────────────────────────────────────────┤ │IRQ3 │COM2 - Serial Communications Port #2 │ ├──────────┼────────────────────────────────────────┤ │IRQ4 │COM1 - Serial Communications Port #1 │ ├──────────┼────────────────────────────────────────┤ │IRQ5 │LPT2 - Parallel Port #2 (Available if │ │ │not using a second printer. Reserved in│ │ │PS/2 systems) │ ├──────────┼────────────────────────────────────────┤ │IRQ6 │Diskette Drive A │ ├──────────┼────────────────────────────────────────┤ │IRQ7 │LPT1 - Parallel Port #1 │ ├──────────┼────────────────────────────────────────┤ │IRQ8 │Real-Time Clock │ ├──────────┼────────────────────────────────────────┤ │IRQ9 │Redirected to IRQ2 ( see note below ) │ ├──────────┼────────────────────────────────────────┤ │IRQ10 │open │ ├──────────┼────────────────────────────────────────┤ │IRQ11 │open │ ├──────────┼────────────────────────────────────────┤ │IRQ12 │PDI Port (mouse port on PS/2 systems, │ │ │and some EISA bus systems. Open if not │ │ │in use.) │ ├──────────┼────────────────────────────────────────┤ │IRQ13 │Math Coprocessor ( if installed ) │ ├──────────┼────────────────────────────────────────┤ │IRQ14 │Hard Disk │ ├──────────┼────────────────────────────────────────┤ │IRQ15 │open │ └──────────┴────────────────────────────────────────┘ Standard I/O addresses and IRQs for COM1 and COM2 o COM1: address = 3F8, interrupt = IRQ4 o COM2: address = 2F8, interrupt = IRQ3 Note: On the IBM-AT (ISA bus) the IRQ9 pin is identical with the IRQ2 pin on the original IBM-PC. If you have an older, 8-bit adapter whose documentation states that it uses IRQ2, then be aware that this will actually be seen as IRQ9 when plugged into the 16-bit ISA bus. The PS/2 also uses this same cascade of interupts. If an error appears saying that COM.SYS or VCOM.SYS is not loaded or that in particular, COM1 or COM2 are not loaded, then it is likely the case that there is an interrupt conflict in the system. Check the settings on the bus mouse card to see if IRQ3 or IRQ4 are set, and if so change the setting otherwise the serial port(s) will not work. If an interrupt or COM port problem is suspected, consult the "OS/2 2.x And Serial Communications" in the REFERENCES section for further information. ═══ 13. OS/2 VERSION 1.3 INFORMATION ═══ Some important notes on os/2 1.3.02; o Family one bus machines use the ....01.sys drivers. o Family two bus machines use the ....02.sys drivers. o Family one uses the AT style adapters cards. o Family two uses PS/2 Microchannel type adapter cards All mouse files are on disk two, and have the extension .sy@. they can be expanded using the unpack command. UNPACK A:MSSER01.SY@ C:\OS2 Note: Latest CSD version is WR05050. The previous version of this system was CSD WR05016. Supported OEM Equipment: The only OEM machine supported on 1.3 is Compaq. Any mouse which is 100% Microsoft compatible is supported, but many of them are untested since they did not exist when 1.3 came out. This creates a bit of a gray area about what is supported and what is not. There is a list below of some which have recently been tested and the statments which they use in CONFIG.SYS. ABIOS patch for the P75: Is dated 12-13-91. It can be forwarded to any customer using OS/2 version 1.x who can not update to OS/2 v 2.0. It includes fixes for several problems including the system hardware problem with the Mouse interface on the P75. OS/2 v2.0 does not require this patch as the corrective code is built into the OS/2 kernel. A CSD sould be available to 1.3 users that has this fix. Please check and see if the file F85200.BIO is available through OS/2 support and that P75 users are instructed to add this module name to their ABIOS.SYS file so that it is loaded. If a P75 user has this file F85200.BIO with the current date of 12-13-91 or later and is still having mouse problems, it is likely that the ABIOS.SYS has not been updated correctly by the user or the install program was not run to include it. This ABIOS patch will prevent 99% of the Wild Mouse failures that normally occur on a P75. It is not 100% effect. Nor will it do any good once the mouse is out of sync but at least it will greatly reduce the failures seen by the customer. P75 customers with this wild mouse problem should also be advised that the old style IBM mouse with the black ball will fail more than others on the P75. If possible, they should swap mice and use the IBM gray ball mouse on P75's.There is nothing wrong with the old style black ball mouse, it will work OK on other systems. It also works OK on the P75 with the ABIOS patch F85200.BIO dated 12-13-91 correctly installed. ═══ 13.1. CONFIG.SYS Statements for Supported Mice ═══ The following panels describe the appropriate CONFIG.SYS and other setup information for various mice, including OEM mice... ═══ 13.1.1. IBM Mouse In PDI Mouse Port ═══ This works using the following statements for PS/2 machines ( family 2 ) DEVICE=C:\OS2\IBMMOU02.SYS DEVICE=C:\OS2\MOUSE.SYS TYPE=IBMMOU$ This works using the following statements for Valuepoint & PS/1 machines ( family 1 ) DEVICE=C:\OS2\IBMMOU01.SYS DEVICE=C:\OS2\MOUSE.SYS TYPE=IBMMOU$ ═══ 13.1.2. Microsoft Inport Mouse w/ Inport Card ═══ With card set on primary address (jumper J1) , IRQ5 (jumper J3), and on normal slot (jumper J2). This works using the following statements in CONFIG.SYS: DEVICE=C:\OS2\MSINP01.SYS DEVICE=C:\OS2\MOUSE.SYS TYPE=MSINP$ Note: MSINP01.SYS is for non-Microchannel bus machines. This card will not work on a Microchannel bus (PS/2 machines). ═══ 13.1.3. Inport Mouse In PDI Mouse Port ═══ This works using the following statements DEVICE=C:\OS2\MSPS201.SYS DEVICE=C:\OS2\MOUSE.SYS TYPE=MSPS2$ Note: MSPS201.SYS is for non-Microchannel bus machines. MSPS202.SYS is for the PS/2 microchannel machines (family 2). ═══ 13.1.4. Inport Mouse In Serial Port ═══ This works using the following statments DEVICE=C:\OS2\MSSER01.SYS SERIAL=COMx ('x' = 1 or 2) DEVICE=C:\OS2\MOUSE.SYS TYPE=MSSER$ Note: MSSER01.SYS is for non-Microchannel bus machines. MSSER02.SYS is for the PS/2 microchannel machines (family 2). ═══ 13.1.5. Microsoft Bus Mouse ═══ Card set on IRQ5. Works with following statements DEVICE=C:\OS2\MSBUSO1.SYS DEVICE=C:\OS2\MOUSE.SYS TYPE=MSBUS$ Note: MSBUS01.SYS is for non-Microchannel bus machines. This card will not work on a Microchannel bus (PS/2 machines). ═══ 13.1.6. MicroSpeed PCTRAC Trackball w/MicroSpeed Card ═══ Card set on PRIMARY address, and IRQ5 works with following statements DEVICE=C:\OS2\MSBUS01.SYS DEVICE=C:\OS2\MOUSE.SYS TYPE=MSBUS$ Note: MSINP01.SYS is for non-Microchannel bus machines. This card will not work on a Microchannel bus (PS/2 machines). ═══ 14. POINTING DEVICE APARS ═══ For open apars, if the customer has a similar problem add them to the IP page of the APAR. The information in the infoapars is not necessarily current. Information in this document should be considered more recent and accurate in case of a conflict. ┌──────────┬────────────────────────────────────────┐ │APAR │APAR Title and Description │ │Number │ │ ├──────────┼────────────────────────────────────────┤ │II06091 │Infoapar - Interrupts and OS/2 V2.0 │ ├──────────┼────────────────────────────────────────┤ │II06079 │Infoapar - Mouse installation and │ │ │configuration │ ├──────────┼────────────────────────────────────────┤ │II06174 │Infoapar - ATI Graphics Vantage Video │ │ │Card with Mouse Port │ ├──────────┼────────────────────────────────────────┤ │II06069 │Infoapar - COM port information │ ├──────────┼────────────────────────────────────────┤ │PJ03802 │Seamless Apps don't recognize left-hand │ │ │mouse setting when both OS/2 :WINOS2 set│ │ │left-handed │ ├──────────┼────────────────────────────────────────┤ │PJ03822 │Problems with serial mouse on HP RS/20C │ ├──────────┼────────────────────────────────────────┤ │PJ04073 │OS/2 supports only one Mouse. (APAR │ │ │CLOSED as suggestion). │ ├──────────┼────────────────────────────────────────┤ │PJ04196 │Selective install does not always remove│ │ │DEVICE statements │ ├──────────┼────────────────────────────────────────┤ │PJ04244 │Logimenu.com will not work in OS/2 VDM │ ├──────────┼────────────────────────────────────────┤ │PJ04275 │Right mouse button select and drag can │ │ │catch wrong icon │ ├──────────┼────────────────────────────────────────┤ │PJ04330 │Mouse hangs at right side of screen │ ├──────────┼────────────────────────────────────────┤ │PJ04351 │Cannot use 3-button mouse PJ04396 L40SX │ │ │mouse frozen after resume if mouse moved│ │ │during suspended state │ ├──────────┼────────────────────────────────────────┤ │PJ04413 │DOS mouse drivers that work in MS-DOS │ │ │5.0 don't work in VDM or VMB │ ├──────────┼────────────────────────────────────────┤ │PJ04415 │Logitech 3 Button Mouse. 3rd button │ │ │doesn't work. │ ├──────────┼────────────────────────────────────────┤ │PJ04429 │8516 Touch screen driver only operates │ │ │with IBM mouse │ ├──────────┼────────────────────────────────────────┤ │PJ04479 │Special program for disabled users has │ │ │sticky keys │ ├──────────┼────────────────────────────────────────┤ │PJ04534 │Kensington Expert Mouse will not work │ │ │with OS/2 V2.0 │ ├──────────┼────────────────────────────────────────┤ │PJ04754 │Mouse Systems PC BUS Mouse won't work │ │ │with OS/2 V2.0 │ ├──────────┼────────────────────────────────────────┤ │PJ04545 │Logitech trackman │ ├──────────┼────────────────────────────────────────┤ │PJ04589 │CHICONI Tracking Keyboard with built in │ │ │3 button trackball │ ├──────────┼────────────────────────────────────────┤ │PJ04611 │Semigraphics tablet will not work in │ │ │OS/2 │ ├──────────┼────────────────────────────────────────┤ │PJ04628 │Mouse will not work with WIN-OS/2 │ ├──────────┼────────────────────────────────────────┤ │PJ04810 │Mouse systems optical mouse │ ├──────────┼────────────────────────────────────────┤ │PJ04812 │Chicony Trackball │ ├──────────┼────────────────────────────────────────┤ │PJ04855 │MS bus mouse will not work under OS/2 │ ├──────────┼────────────────────────────────────────┤ │PJ04866 │Mouse pointer lost in WINOS2 │ ├──────────┼────────────────────────────────────────┤ │PJ04904 │Toshiba Docking Station hot plug mouse │ │ │problem (acts like wild mouse problem) │ ├──────────┼────────────────────────────────────────┤ │PJ04921 │Emerson E-mouse erratic under dos VDM │ │ │sessions │ ├──────────┼────────────────────────────────────────┤ │PJ05254 │Logitech C7 mouse will not work with OS2│ │ │v2.0 │ ├──────────┼────────────────────────────────────────┤ │PJ05310 │Mouse support problem with WORD4 on VGA │ │ │machine │ ├──────────┼────────────────────────────────────────┤ │PJ05615 │Mouse sluggish in WINOS2 when plotting │ │ │in background │ ├──────────┼────────────────────────────────────────┤ │PJ05681 │PC Mouse Systems mouse unusable in │ │ │WINOS2 │ ├──────────┼────────────────────────────────────────┤ │PJ05730 │Mouse Systems serial mouse won't work │ │ │with DOS apps in OS/2 │ ├──────────┼────────────────────────────────────────┤ │PJ05799 │Mouse disappears with video notification│ │ │on when t/r ram size set to 64k on AMI │ │ │boards │ ├──────────┼────────────────────────────────────────┤ │PJ05853 │8516 touch screen display gets video │ │ │corruption when running windows apps │ ├──────────┼────────────────────────────────────────┤ │PJ05896 │Kurta, Summagraphic : other tablets │ │ │won't work with os/2 │ ├──────────┼────────────────────────────────────────┤ │PJ06011 │Incorrect touch and mouse events │ │ │returned from touchscreen APIs in OS/2 │ ├──────────┼────────────────────────────────────────┤ │PJ06201 │Mouse event handler gives incorrect │ │ │results when run from an OS2 window │ ├──────────┼────────────────────────────────────────┤ │PJ06259 │Mouse Systems bus mouse and other OEM │ │ │bus/serial cards will not work with OS/2│ │ │2.0 │ ├──────────┼────────────────────────────────────────┤ │PJ06273 │Mouse won't work after resume from power│ │ │down on L40SX laptop │ ├──────────┼────────────────────────────────────────┤ │PJ06299 │MS mouse exhibits jerky movement │ ├──────────┼────────────────────────────────────────┤ │PJ06309 │Mouse pointer changes shape when on last│ │ │page of settings in notebook │ ├──────────┼────────────────────────────────────────┤ │PJ06550 │Problems with mouse pointer disappearing│ │ │in WINOS2 after service pack │ ├──────────┼────────────────────────────────────────┤ │PJ06826 │Deluxe Paint enhanced pixel movement is │ │ │wrong │ ├──────────┼────────────────────────────────────────┤ │PJ07239 │Mouse very sluggish on large (19") │ │ │moniters │ ├──────────┼────────────────────────────────────────┤ │PJ07264 │Microsoft mouse jumpy/erratic after │ │ │service pack on IBM mod70 w/8513 display│ ├──────────┼────────────────────────────────────────┤ │PJ07360 │ │ ├──────────┼────────────────────────────────────────┤ │PJ07916 │Erratic or jerky mouse pointer movement │ │ │on mod 90 : 95 running at greater than │ │ │33 mhz ... │ ├──────────┼────────────────────────────────────────┤ │PJ08030 │Unatended start mode using power on │ │ │password disables mouse plugged in mouse│ │ │port │ ├──────────┼────────────────────────────────────────┤ │PJ08043 │Mouse driver not working with Microspeed│ │ │bus card │ ├──────────┼────────────────────────────────────────┤ │PJ08206 │Mouse driver will not recognize Mouse │ │ │Systems Serial/Bus card. │ ├──────────┼────────────────────────────────────────┤ │PJ08292 │ATI Mouse not working after CSET/2 │ │ │installed │ ├──────────┼────────────────────────────────────────┤ │PJ08293 │ATI Graphics Ultra mouse right button │ │ │functions not all working │ ├──────────┼────────────────────────────────────────┤ │PJ08411 │PS/2 style mouse port does not work on │ │ │OEM notebook pc's │ ├──────────┼────────────────────────────────────────┤ │PJ08854 │Button mappings incorrect for 3-button │ │ │mouse when used as left handed │ ├──────────┼────────────────────────────────────────┤ │PJ08908 │After install of 2.1, mouse will not │ │ │work on reboot unless first unplugged │ ├──────────┼────────────────────────────────────────┤ │PJ08909 │Mouse fails on resume from power down on│ │ │IBM Thinkpad 700c │ ├──────────┼────────────────────────────────────────┤ │PJ08916 │Mouse lost on reboot after install on │ │ │version 2.1, due to install of other │ │ │system mouse driver into c:/os2 │ └──────────┴────────────────────────────────────────┘ ═══ 15. POINTING DEVICE MODELS & MANUFACTURERS ═══ ┌────────────┬──────────────────┬──────────┬────────┬────────┐ │Company Name│Devices │MS │Interfac│IRQs │ │ │ │Compatible│ │Supporte│ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │Amazing │AMX-300 mouse │Yes │S, B, P │? │ │Technologies│ │ │ │ │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │Amazing │AAK-300 trackball │Yes │S, B, P │? │ │Technologies│ │ │ │ │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │Appoint │Mouse Pen │Yes │S, P │3, 4 │ │ │Professional │ │ │ │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │Appoint │Thumbelina │Yes │S, P │3, 4 │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │Antec Inc. │Artec-21 Plus │Both │S │3, 4 │ │ │Mouse │ │ │ │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │Calcomp Inc.│Wiz Mouse System │No │S, P │2, 3, 4,│ │ │ │ │ │5 │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │Chicony │Keyboard w/ │Both │S │4 │ │America Inc.│trackball │ │ │ │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │CH Products │RollerMouse │Yes │S, B, P │3, 4 │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │CMS │CMS Mini Mouse │No │S, B │2, 3, 4,│ │Enhancements│(standard) │ │ │5 │ │Inc. │ │ │ │ │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │CMS │CMS Mini Mouse │No │S, B │2, 3, 4,│ │Enhancements│(hi-res) │ │ │5 │ │Inc. │ │ │ │ │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │Commax Inc. │Witty Mouse │Both │S │0, 3, 7,│ │ │ │ │ │8 │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │Commax Inc. │Fancy Mouse │Both │S │0, 3, 7,│ │ │ │ │ │8 │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │Commax Inc. │Witty Ball │Both │S │0, 3, 7,│ │ │ │ │ │8 │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │Computer │Trackball Plus │Both │S │1, 2 │ │Products Co.│ │ │ │ │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │Dell │Dell Serial Mouse │Yes │S │4 │ │Computer │ │ │ │ │ │Corp. │ │ │ │ │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │DFI Inc. │DMS-200 Mouse │Both │S │3, 4 │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │DFI Inc. │DMS-200H Mouse │Both │S │3, 4 │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │DFI Inc. │DMS-400 Mouse │Both │S │3, 4 │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │Evergreen │Diamond 24 │Yes │S, B, P │? │ │Systems │trackball │ │ │ │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │Evergreen │Diamond 20 │Yes │S, B, P │? │ │Systems │trackball │ │ │ │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │Evergreen │Omega │Yes │S, P │? │ │Systems │ │ │ │ │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │Focus │Focus FT-100 │Both │S │1, 2 │ │Fulcrum │Tracker │ │ │ │ │Corp. │ │ │ │ │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │GRID Systems│GRID IsoPoint │Yes │N/A │3, 4, 5 │ │Corp. │ │ │ │ │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │IBM Corp. │IBM PS/2 Mouse │Yes │P │12 │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │IBM Corp. │PS/2 Trackpoint │Yes │P │12 │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │IMSI │IMSI Mouse │Yes │S, B │? │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │IMSI │PET Mouse │Yes │S, B, P │? │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │Internationa│The Mouse Pen │Yes │S, P │0, 3, 4 │ │Machine │ │ │ │ │ │Control │ │ │ │ │ │Systems │ │ │ │ │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │ITAC Systems│Mouse-Trak (ball 2│Both │S, B, P,│3, 4, 5,│ │Inc. │button) │ │I │7,10,11,│ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │ITAC Systems│Mouse-Trak (ball 3│Both │S, B, P,│3, 4 │ │Inc. │button) │ │I │ │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │ITAC Systems│Mouse-trak (ball) │Yes │S, B, P │? │ │Inc. │Industrial │ │ │ │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │ITAC Systems│Mouse-trak (ball) │No │S, B, P │? │ │Inc. │Professional │ │ │ │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │Kensington │Expert Mouse │Yes │P, B, P │2, 3, 4,│ │Microware │ │ │ │5,7,10,1│ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │Key Tronic │Professional │Yes │S,B │2, 3, 4,│ │Corp. │Series Mouse │ │ │5 │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │Kraft │Kraft Trackball │No │S │3, 4 │ │Systems │ │ │ │ │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │Kraft │TopTrak Trackbal │Yes │S │3, 4 │ │Systems │ │ │ │ │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │KYE │Genius Mouse GM-6X│Both │S │1, 2, 3,│ │Internationa│ │ │ │4, 5 │ │Corp. │ │ │ │ │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │KYE │Genius Mouse │Both │S │1, 2, 3,│ │Internationa│GM-6000 │ │ │4, 5 │ │Corp. │ │ │ │ │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │KYE │Genius Mouse │Both │S │1, 2, 3,│ │Internationa│GM-F301 │ │ │4, 5 │ │Corp. │ │ │ │ │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │KYE │Genius Mouse │Both │S,P │1, 2, 3,│ │Internationa│GM-F302 │ │ │4, 5 │ │Corp. │ │ │ │ │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │KYE │Genius Mouse │Both │S,P │1, 2, 3,│ │Internationa│GM-F303 │ │ │4, 5 │ │Corp. │ │ │ │ │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │KYE │Genius Mouse GM-S2│Both │P │1, 2, 3,│ │Internationa│ │ │ │4, 5 │ │Corp. │ │ │ │ │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │KYE │Clix Mouse │No │S, B, P │? │ │Internationa│ │ │ │ │ │Corp. │ │ │ │ │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │KYE │Clix Plus mouse │No │S, B, P │? │ │Internationa│ │ │ │ │ │Corp. │ │ │ │ │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │KYE │Genie Track │0 No│S, B, P │? │ │Internationa│(ball)GK-T32 │ │ │ │ │Corp. │ │ │ │ │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │Lightwave │Lester the │e │S, B, P │? │ │Technologies│Cordless Mous │Yes │ │ │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │Liuski │ProCorp Mouse │No │S │2, 3, 4,│ │Internationa│ │ │ │5 │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │Liuski │ProCorp Mouse │No │B │2, 3, 4,│ │Internationa│ │ │ │5 │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │Logitech │See Logitech │ │ │ │ │Inc. │section of this │ │ │ │ │ │document │ │ │ │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │Logitech │Dexxa Mouse │No │S, B │2, 3, 4,│ │Inc. │ │ │ │5 │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │Lynx │Lynx Turbo │No │S, B, P │2, 3, 4,│ │Computer │Trackball │ │ │5 │ │Products │ │ │ │ │ │Inc. │ │ │ │ │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │Magitronic │Procorp Mouse │No │S, B, P │? │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │Marconi │Marcus Trackball │Yes │S, B │2, 3, 4,│ │Circuit Tech│RB2-305 │ │ │5 │ │Corp. │ │ │ │ │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │ │Marcus Trackball │Yes │S, B │2, 3, 4,│ │ │RB2-306 │ │ │5 │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │Microcompute│IMSI Mouse │Yes │S, B │4 │ │Software │ │ │ │ │ │Inc. │ │ │ │ │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │MicroSoft │MicroSoft Mouse │Yes │S, B, P,│2, 3, 4,│ │Corp. │ │ │I │5 │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │ │BallPoint │Yes │S, P │All │ │ │Trackball │ │ │(0-15) │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │MicroSpeed │PC-Trac Trackball │Both │S, B, P,│2, 3, 4,│ │Inc. │ │ │I │5, 7 │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │ │FastTRAP Trackball│Both │S,B │2, 3, 4,│ │ │ │ │ │5, 7 │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │ │MicroTRAC │Yes │S, P │? │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │Mouse │PC Mouse │No │S, B, P │2, 3, 4,│ │Systems │ │ │ │5, 7 │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │ │PC Mouse II │Both │S, B │2, 3, 4,│ │ │ │ │ │5, 7 │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │ │PC Mouse III │Both │S, B, P │2, 3, 4,│ │ │ │ │ │5, 7 │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │ │OmniMouse II │Yes │S, B │2, 3, 4,│ │ │ │ │ │5, 7 │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │ │The White Mouse │Both │S, B, P │2, 3, 4,│ │ │ │ │ │5, 7 │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │ │PC Trackball │Yes │S, P │2, 3, 4,│ │ │ │ │ │5, 7 │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │ │The Little │Yes │S, P │2-15 │ │ │Mouse/PC │ │ │ │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │cumonics │Manager Mouse │Both │S │1, 2, 3,│ │Corp. │Cordless │ │ │4 │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │ │Manager Mouse │Both │S │1, 2, 3,│ │ │ │ │ │4 │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │Penny : │TrackerMouse TM1 │No │S, P │3, 4 │ │Giles │ │ │ │ │ │Controls │ │ │ │ │ │Inc. │ │ │ │ │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │ │TrackerMouse TM1 │No │S │3, 4 │ │ │Plus 16 │ │ │ │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │ │TrackerMouse TM1 │No │S, P │3, 4 │ │ │Plus 32 │ │ │ │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │ │TrackerMouse II │Yes │S, B, P │? │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │Practical │The Cordless Mouse│No │S, P │3, 4 │ │Solutions │ │ │ │ │ │Inc. │ │ │ │ │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │ProHance │ProHance Power │No │S, B │All │ │Technologies│Mouse 50 │ │ │ │ │Inc. │ │ │ │ │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │ │ProHance Power │No │S, B │All │ │ │Mouse 70 │ │ │ │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │ │ProHance Power │No │S, B │All │ │ │Mouse 100 │ │ │ │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │ │ProMouse │Yes │S, B │? │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │ │PS/2 Trackball │Yes │P │? │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │ │PowerTrack (ball) │No │S, B │? │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │Qtronix │Might Cat Mouse │No │S, B, P │? │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │ │Cordless Mouse │No │S, B, P │? │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │ │TB-90 Trackball │No │S, B, P │? │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │ │TB-90 Trackball │No │S, B, P │? │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │Qualitas │Samurai Mouse │Yes │S │3, 4 │ │Trading Co. │ │ │ │ │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │SmarTEAM │SmarTEAM Mouse │Yes │S, B │None │ │Inc. │ │ │ │ │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │Suncom │MouseTrac │? │S │3, 4 │ │Technologies│Trackball │ │ │ │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │ │SunMouse │? │S │3, 4 │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │ │ICONtroller │Yes │S │3, 4 │ │ │mini-joystick │ │ │ │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │ │Crystal Mouse │Yes │S │? │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │Tandy Corp. │Tandy Serial │Yes │S │3, 4 │ │ │Mouse │ │ │ │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │ │Tandy 2-button │Yes │P │0 │ │ │Mouse │ │ │ │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │Zeny │Zen Mouse │No │S │? │ │Computer │ │ │ │ │ │Systems │ │ │ │ │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │Z-Nix │Z-Nix SuperMouse │Yes │S, B, P │? │ │ │II │ │ │ │ ├────────────┼──────────────────┼──────────┼────────┼────────┤ │ │Z-Nix Cordless │Yes │S, B, P │? │ │ │SuperMouse │ │ │ │ └────────────┴──────────────────┴──────────┴────────┴────────┘ For further information reference PC Magazine August 1990 pgs 211-277, PC World May 1992 pgs 140-147, Yes=Microsoft compatible, No=Non Microsoft compatible, Both=Microsoft and Mouse Systems compatible S=serial, B=bus, P=PDI port (PS/2 port), I=inport ═══ 16. REFERENCES ═══ ──────────────────────────────────────────────────────────── Author Title Publisher Issue ────────────────────────────────────────────────────────── Deitel, H. "The Design Of OS/2 Addison Wesley 1992 M., : (32 Bit OS/2)" Kogan, M. S. ────────────────────────────────────────────────────────── Flynn, M. "Mice : PC Magazine August K. Trackballs... 1990, pp. Choices for the New 211-277. Generation of Applications" ────────────────────────────────────────────────────────── Howard, B. "Field Mice... PC Magazine October Different, Yes. 15, 1990, Better, Maybe." pp. 111-133 ────────────────────────────────────────────────────────── IBM "OS/2 2.0 Technical International First Library Physical Business Edition Device Driver Machines Corp. 1992, IBM# Reference Version 10G6266. 2.00" ────────────────────────────────────────────────────────── IBM "OS/2 2.0 Technical International First Library Virtual Business Edition Device Driver Machines Corp. 1992, IBM# Reference Version 10G6310. 2.00" ────────────────────────────────────────────────────────── IBM "OS/2 2.0 Tips : IBM September IBM# Techniques" 1992 53G1930. ────────────────────────────────────────────────────────── IBM 'Red "International International April Books' Technical Support Business 1992, IBM# Centers, OS/2 Machines Corp. GG24-3731- Version 2.0 Volume 2: DOS and Windows Environment" ────────────────────────────────────────────────────────── Lincoln, "Keyboards, Mice, PC World June 1990, S. : and Trackballs With pp. Lusty, S. The Personal Touch" 166170. ────────────────────────────────────────────────────────── Mastriani, "Writing OS/2 2.0 Van Nostrand 1992. S. J. Device Drivers In C" Reinhold ────────────────────────────────────────────────────────── Smith, C. "Input Devices" PC World May 1992, pp. 140-147. ────────────────────────────────────────────────────────── Schoeller, "OS/2 2.x and Serial IBM Warranty May 1993 P. Communications" Support Document ────────────────────────────────────────────────────────────